Slightly routine but fun though
Slightly routine but fun though
loved it but...
great game really fun but i wish he didnt do start and stop movements and the sounds get annoying. also when the commands dont work correctly after running it automatically clears the command list which is SUPER ANNOYING! i stopped playing because it cleared my commands when i only missed one forward block...
This game idea is really cool, but there's a few things bothering me in this version.
The robot and the blue field look terrible! Though I do love the pixelated green background and control panel. The sound that the robot makes when it moves is very annoying in my opinion.
Also, it would have been nice to get some flow in the programming. Now the robot is executing one step at a time, then stops, then performs the second step, even if you program it to move a couple of blocks in the same direction. Another thing that bothered me was the fact that you can't call the first subroutine in the second one; for some reason you can only call the second subroutine in the first one. Why?
Lastly I want to mention that you should also be able to drag a command out of the main program / routine again; now you have to press clear and you lose all command inputs.
I hope you consider this as constructive criticism; that's how I mean it. Good luck with it; hope to see a Bill the Robot II someday.
Hahaha, yeah I'm afraid I'm not much of an artist. In my defense, something about the way Newgrounds embeds the content is screwing up my tiles, shaving off the last (or maybe the first) row and column of pixels. Rest assured that Bill has undergone a number of redesigns, and won't look quite so much like a penis in the next version.
Regarding Bill's start-stop nature; I don't really have much of an excuse other than to say it was done this way on purpose. My target audience for this was 8 and 9 year olds, so I removed as much complexity as I could; including recursion and command arguments. To be honest I kind of like the limitation though, because part of the challenge is coming up with a solution that makes up for the "hardware" limitations.
I agree it is pretty lame that you can't remove commands from Bill's program, but if it helps, you can just overwrite a command with something else, or just the empty command.
Thanks for playing!
like it, but..
I like the game a lot, but maybe it's an idea to make it possible to stop the robot when you see that you've made a mistake.
Now you have to wait so long till he runs out of moves....
Putting the fun back in functions!
I recall LOGO, but this definitely reminded me of LightBot more... this isn't a bad thing however. I love this style of game and more levels = more fun for me!
There were a few things that bothered me though. The speed is definitely an issue. I can understand wanting the third graders to be able to correct any errors by watching the robot and following along with the code, but there should be an option to speed things up. This was especially needed after making a small error after a particularly long level.
"I quited after 2nd level because in this game a sabroutine cannot call itself an the 2nd sabroutine cannot call the 1st" - Ahh, that should be changed and more advanced, recursive levels added?
A level count and running tally of how many commands were used would entice people to use the functions more efficiently. Maybe the most efficient number of commands would be known and people could try to match it; if you were close to the number, the efficient code would be made known so people could learn from it.
Power to the programmers!