EEPROM by bentglasstube
A robot with no microcode isn't very useful at all. Collect instructions and navigate through a perilous robot factory.
I had very little time to work on this game so it's quite unfinished. I meant to include instructions in game as well as have blocks be pushable. I'm not even sure if all the levels are able to be completed.
Instructions:
Use the arrow keys to write a program into the robot to navigate the levels.
NOP - Nothing, you start with this.
MOV - Move the direction the robot is facing.
SHL - Shift left, turn to the left.
SHR - Shift right, turn to the right.
POP - Remove the last instruction.
RST - Reset the entire program.
EXECUTE - Run your program, see where the robot winds up.
The goal in each stage is to exit. You have limited memory with which to write your program, and the program will loop at the end, and you might have to use this to your advantage.
Ratings
| Overall | 233th | 3.46⭐ | 27🧑⚖️ |
| Fun | 264th | 3.2⭐ | 27🧑⚖️ |
| Innovation | 217th | 3.36⭐ | 27🧑⚖️ |
| Theme | 410th | 2.875⭐ | 26🧑⚖️ |
| Graphics | 152th | 3.6⭐ | 27🧑⚖️ |
| Given | 32🗳️ | 0🗨️ |
```
In file included from box.cc:1:
./box.h:5:10: fatal error: 'graphics.h' file not found
#include "graphics.h"
^~~~~~~~~~~~
1 error generated.
make: *** [output/box.o] Error 1
```
I have added percompiled version for Windows and linux. I will do a better packaging of the Linux one later as well as adding an OSX version.
I can easily see how you could expand on this, adding more tasks to complete other than just getting to the exit, and more puzzles that require you to make your code function while looping.
You could probably gracefully borrow zachtronics games 'JMP' functions to make more complex code, if you decided to keep working on this.
Oh, and I like the very literal interpretation of the theme.
I definitely wanted to add a lot more to this game but my wife injured herself and I was only able to spend about 16 hours on this entry. It's hard for me to stay motivated to work on things post jam but this one is incomplete so I really should finish it up.
The pusher cubes seem to visually glitch out for a frame at full extension.
Deleting all your code if you messed up is annoying, and overall more normal text editor would probably be a much better interface than a stack.
The complete lack of any control flow or interactable parts makes it so there isn't really much challenge to the actual gameplay part.
I like the basic idea, but I think you needed a lot more time to make it good.
Instructions weren't clear what each command did so I struggled to understand exactly what I was programming and thus used trial and error but then when I failed I couldn't reset the level.
Overall fun game but a little frustrating as it wasn't 100% clear how the commands worked and specificially the timing.
Edit: Now I see the instructions on this page. You should add them to the game intro so players know.