Thanks for your comments guesst.
So I cracked open the code to check it out and had a few things:
- You define a bunch of const ints for map generation and then don't use them. It would make your code much prettier.
Yeah; there was a sort of trade of in my head between writing nice code and getting the game done. Given it was so small I didn't feel any obligation to make it very sexy code. Or neat code.
- You have a ton of global variables each defined each on its own line. That would be fine if you were commenting on the usage of each one, but even then I'd combine many of them to share a definition line with others. Group them somewhat.
I don't like declaring variables on different lines. I find them easier to read through if they're on different lines. It's a personal preference maybe, but I really feel it quite strongly.
As it's currently set up you can only have one boulder at a time. You're missing out on alot of potental robustness, tho to tell the truth one was more than enough.
Yeah. I considered making things all nice and object-oriented, but...given that I decided that you would only be in one room at once, and that the room should be small to give the reflections screen-space to show themselves, there wasn't much point in putting the whole OO framework in. And also the 1-room system meant that I didn't really need two boulders.
- You mentioned pushable objects. That would be great!
I can think of a couple of extra puzzles I'd be able to add in if I enabled pushable objects. Hmm. Would increase the complexity of the code; maybe to the extent where it would have been better to do stuff using an OO approach. I'm not really interested on working on this project at the moment though.
- Another cool feature would be the ability to turn rooms 90o left or right. It would be a departure from the portal of it's roots, but it could add a considerable level of robustness. Also I don't know how you can represent that with the blocky tile set, which I absolutely love.
tileset? I don't know to what extent a bunch of hard-coded fillrects constitute a tileset
But I'm glad you like them: I also like them.[/list]