E:\dev\PyWeek3\Dev>wc *.py
  137   178  3022 bandMember.py
    7    21   121 behavior.py
   44    69  1087 boundingBox.py
   15    14   233 commonMath.py
  466   618 11801 fan.py
   42    83   978 goal.py
   72    52  2126 loadSounds.py
  158   261  4343 main.py
   42    33   590 objectLists.py
   96   135  2029 obstacle.py
   22    39   468 soundMgr.py
 1101  1503 26798 total

If you had asked me to guess how many lines of code I had written on this today, I probably would have gone higher than this.

I expect that I won't write as much code per day during the week - in part because I won't have as much time, but also because as the project gets closer to the end, I expect to spend time replacing my OpenGL stick figure art with something more presentable.

Hm, there's even the danger that as I remove programmer (code) art and replace it with programmer (drawn) art, my lines of code will go down.

I've completed the basic game I set out to make when I started:

1. You're a rabbit who's hungry and can eat food from a garden,
2. The farmer will notice and try to catch you, and
3. You can hide from the farmer by digging underground.

The game detects when you've been caught and when you've eaten enough to satisfy your hunger.

I also got the level editor mostly working today -- I couldn't get picking working while drawing the map in perspective so I switched back to ortho, and the lighting worked. No idea why it works now and didn't before. My next step is to bring up a little menu with actions (rotate, delete, move) when you click on an object in the map.

I have some additional ideas for gameplay, but I'd welcome suggestions. First up will be the introduction of a "hard" mode which has a timer, and you must eat up before the timer runs out.

Also the collision detection / response is a little dodgy in places and I'd like to clean it up...

Well day 2 did not feel as productive as day 1. Spent most of the day trying to get a 2d faux-3d scaling thing to work and started on a couple of the procedurally generated background elements in the game. I guess I did actually write a fair bit of code; it just doesn't do that much on the screen. Today I will be focussing on procedurally generated backgrounds, and putting some pick-up-able items in the game.

sloccounts says:
Total Physical Source Lines of Code (SLOC) = 276
Total Estimated Cost to Develop = $ 6,992

That's a lot of money for two days work!

Remember the Master was an important Member to the ANZ Empirites ...

I just uploaded the current release of "The World Dissolved," which just contains Act 0. Which is, of course, just setup and the like. Not that there's going to be a whole lot of interactivity in the end, mind you. But this will give you a taste.

After hitting a glitch with pgu's FileDialog (whether the glitch is with me or with pgu, I am not readily sure), I am scrapping its use (FileDialog, still using pgu) and moving to a cludge, why pick what you can hard code. This is a specific use utility, not general purpose, so hardcoding, though icky, is perfectly reasonable given the time frame. Maybe I'll have time to revisit the issue when time is not so fleeting.

Other than that, I have heard good things from Skaro about our game engine, so I figure we are making good progress. It's only Monday. I'll panic Wednesday, then think we're doing amazingly well on Thursday. Then it will be a full out fit of activity until the deadline.

So says I.

Was my fault, when i see the Demo, in a visual way it seems to be wrong because it work in a different way when finds a path under or over a diagonal wall, but it seems to be only an ilussion because of the way the map is draw, sorry for the time, thanks

a warning for the people who attemps to use the library (http://www.pygame.org/projects/9/195/). the library is not working. i'll upload an snapshot

So I finally came up with what I'm going to do for this. It's going to be an interactive novel. On the plus side, that means I get to flex my writing muscles over the next week. On the minus side, that means I have to flex my writing muscles over the next week.

I don't plan on having any graphics in the game. And the code is already horrid, barely an hour or two into my starting. Ah, well. I've been meaning to write some form of IF for ages, and it looks like this is going to be where I do it.

Another plus: I suspect that there will be very low system requirements to play the game.

I've reached a build that's actually playable - I can win or lose the game now. There's much that remains to be added, including angle of vision on the opponents, dialog boxes, music, menus, splash screens, the store interface, the "weapon" system, and savegames.

But you know, not so bad for a day's work.