Here’s my first screen shot:
Just kidding, that’s my entry Unmutate from Pyweek 13.
I haven’t made anything for this LD yet, but I might possibly make a sequel or remake of that game.
It just seems sorta silly that the theme for Pyweek 13 was Mutate and now the theme for LD is Evolution, but whatever.
Since more people play web games, I should make a web game. But I have very little experience in web games, so it’ll be text adventure game…
I finished my game in time for the jam. http://www.ludumdare.com/compo/ludum-dare-22/?action=preview&uid=1044
If you thought that my last compo typing game was bad, this is a morse code game.
I’m an evil game designer… and loving it.
The only button that works is the spacebar.
Here’s my idea for a game so far.
There’s this lonely earthling, so she sends a moon rover to the moon to look for life.
For maximum signal strength, the moon rover has one lonely button, so one must tap it in certain sequences to get the moon rover to move.
As usuall, I’ll be hacking something together in ansi C with SDL.
Vim is the only tool I plan on using, and as such, my games will most likely have pixel art sown into the source.
I’m ready to start hacking. Perhaps my game will even be psuedo 3d with oblique projection.
Cosmologicon and I have been talking over at pyweek about code review and he thought that if other people looked at each other’s code during the compo they could help each other out.
So I had the idea that there should be a game compo where everyone starts making a game and then they switch code with someone else and start working on each other’s game. Every day or so they’d switch code with someone new, and at the end of 7 days everyone would have a frankenstein of a game. People would practice reading other people’s code and in turn writing readable code for others to read.
EDIT: Here’s a link to the pyweek discussion which has now become a code review event.
I’m kinda slow at developing games because I get tangled up in the collisions and stuff. By next compo I’m gonna make a game engine.
I feel guilty making such a hard torturous game. It wasn’t supposed to be this way, so maybe I’m slowly becoming an evil game designer. Mwahahahahaha. Forcing people to type at lightning speeds is downright cruel, I should’ve at least eased them into it better. Oh well, I better be less evil next time.
For my entry the level was stored in RAM as an array of characters, and each character held 8 blocks, which means that each block only took 1-bit (on or off). So theoretically a level 1000 x 1000 would take 125 kilobytes, a 10,000 x 10,000 level would take 12.5 megabytes in RAM.
Ofcourse, saved as a text file that’s easy to edit in notepad, the same file would take over 8 times as much space.
It’s not quite as finished as I would have hoped, but it’s playable and interesting. I just didn’t have enough to make “cool” graphics.
I was so budgeted for time I finished it with 16 minutes to spare.
To play you have to type commands and then Esca (The purple rectangle) will execute them. The goal is to escape from illiteracy.
Perhaps I’ll make a post compo version later.
I’ll probably end up doing something in C and SDL and maybe Lua if I feel like the type of game I’m making would be enhanced by it. I’ll probably draw the graphics in Inkscape and Gimp. The audio will be done in either Audacity or Sox.
I hope I don’t get brought down by crazy bugs like I did last compo. :'(
I should start getting my math figured out right away so that doesn’t happen.
EDIT: Why does it keep autocorrecting my C tag to C++?
So far I’ve been trying to rewrite some example tiling and level code I made before the compo. And since I didn’t want to cheat and look at it, I’ve encountered some bizarre bugs that I didn’t have before. Well, I’ll have to do some serious coding tomorrow.
Maybe I should enter the Jam instead.