Although it took some time to settle on exactly how we'd handle the theme, we seem to have settled on a workable idea. In the true spirit of mad science, it's an epic quest to work up from a humble lab to a true global threat by the power of resource management and careful choices of short term objectives.

We don't have a user interace yet, although work on that is progressing. We did add a simple debugigng aid to allow us to poke at bits of the game state, so we can test that things work, so we can at least show that.



We did add a fair amount of the basic game logic and flow, and the designs looking quite clean (although that will probably change by the end of the week), so we should be able to add extra content fairly easily and quickly.

We also have some tests, and they even pass, so that's nice.

This pyweek, I will be at a disadvantage of time.  I was busy all day Saturday and will not have any time on Tuesday to work at all.  I'm not too worried about it, but it adds a bit of pressure (which I like) to get something produced.  I'm a little dissapointed with the theme this time.

After some more hours of programming, a lot of new functionalities have been added to the game's base, namely on the Entity, Actors, Brain and Input handling.

Some notes on potential sources of wasted time:

• Brain class: I wonder if I'll ever actually use the Brain class for anything other than the main character, but it feels safe to have it around. It's the kind of thing I've grown accostumed to having and it gives me the opportunity to easily change mob behavior or create mobs that mimic the player-controlled character (just give them the same brain, for example).
• Input class: I might never support anything other than Keyboard in the game, but having this between the actual input handling and the rest of the game should make it easy to support different keyboard schemas and perhaps even joysticks.
• Level class: I added some code to handle multiple layers in the level maps. I plan at some point to use the multiple layers to implement certain scenario changes, as well as enabling and disabling passages. But it might turn out that I don't have such features at all.
• constant.py/utils.py: I've been bouncing back and forth regarding where certain functions/constants should be located. Ideally, if constants are used in only one file, they belong there, as well as utility functions. It sort of becomes difficult to determine in advance whether those things are going to get used in only one place when you just sit and start programming rather than plan ahead.

So, this is my second pyweek. Last one I didnt finish because I had too much at work.

Today I got a great start, it wasnt my favorite theme that won but after thinking about it for a while I decided that I would make a tower defense game. Not very original but I thought it would be fun to create :)

Started the day by getting some framework code up and running to handle my rendering, input, and game-management.

After that I started thinking about a map-format and wrote a parser for it. Sweet! My maps are rendering!

Just finished my pathfinding-algorithm and now the enemies know where to go :)

Its been a long day and I seem to have gotten a flying start, alot of work got done fairly quickly!

Dont know how much work I will be able to get done in the week but I think my next goal is to get some basic tower-action going!

/ Tommy

We have decided the theme of the story and so the gameplay type : It's halfway between a tower defence and an action fps from the top, but we can make some change to the end.

The story plot will come early, stay tuned!!! :D

This first screenshot of game

Completely new to pygame but giving pyweek a shot.  Started off by working through a tutorial:

http://qq.readthedocs.org/en/latest/index.html

Dropped about an hour and a half on it and feel like I'm starting to get a little bit of Pygame.  Still no real idea for the game itself.  Potentially some kind of science themed RPG.

It's been a long day and I'm taking a break. After an hour or two, I'll resume work. Here's the status on my code:

Graphics: As done as they need to be at the moment.
Level: Partly done.
Entities and actors: Prototyped.
Brains: just mentioned,
Engine: just mentioned.
Timers: Done.
Events: not even mentioned yet.

Not much about the game style yet, but it is likely to use RPG Maker sprites and tilesets to spare me the trouble of doing graphics. =|

Decided on mad-scientist gladiator theme.

I wish I didn't have to work this week. Only scribbled some concept art so far but already love my game, so I do hope I can get something done.

The idea is rather simple. You're a mad scientist in your mad science lab and build a mad device for which you need mad ingredients and parts. Which are scattered across the lab. There's also your helper a mad yellow elephant which may be real or just your imagination but who is needed to solve most of the puzzles.

Anyway, so far I have an empty .py file importing Allegro 5. The TODO list is:

• create placeholder isometric block (sunday)
• write isometric engine (sunday and evenings monday through friday))
• create first room (friday)
• create more rooms and items (saturday)
• replace placeholder block with better art (saturday)
• add simple two-step animation for scientist and elephant (saturday)
• (if time left) add title menu, finish up all rooms, add sounds, add music