Didn't finish
j-1 on 2009/05/03 12:19
of Camel Walrus Studios
My personal goals with this Pyweek were:
1) Simple concept
2) No planning before the final theme was announced
3) No storyline!
4) Finish within a day or two, and spend the rest of the week looking for bugs
Yet, the first thing I did was to start on code for telling the storyline. The whole week, on my part, was a story of over-engineering. I wrote an isometric tile engine, when we really didn't need one. Because of said tile engine, I had to write a level editor. I didn't have time or energy to make it useful (you can only place tiles, and no enemies or structures), so it ended up a lump of code that just takes up space and actually restricts the rest of the game. This took the whole week. Meanwhile, Jakob began on the real gameplay. The thought was that we were going to meet up somewhere in the middle, and have a working game. We didn't. I wish I had been more active in the game development, but I wasn't. All the credit for the actual game should really go to Jakob and the artists.
Our game idea wasn't innovative, but I thought it was a pretty neat idea. Basically, you are a sheep, that is going to tear apart the human world of concrete and plant a lawn instead. The grass would spread on it's own from ruined buildings (in much the same way as Zerg Creep in the Starcraft games). Evidently, none of this was really implemented, and you just drive around and fight humans on a gigantic lawn. Most of this was hacked together in the last minute. If only we had had three or four more days, we could have made a game, instread of this demo, but alas.
Looking at the storyline that Clueless wrote, I can see how great this game could have become. Even though it was ambitious and didn't fit with my original goals, I still think we could have made it. Our team had four active members, more than in the previous competitions. What we lacked was a good plan regarding the codebase.
Ah well, there's nothing to do about it now. Thanks everyone, for a fun and inspiring week!
(log in to comment)
Comments
j-1 on
2009/05/04 19:11:
I think the bug came when we enabled sound effects, so disabling them might function as a work-around.
cyhawk on
2009/05/05 08:27:
This patch allowed me to finish the game and get "I think you won! Congratulations!" :)
cyhawk on
2009/05/04 16:28:
I often get a crash with this exception:Traceback (most recent call last): File "c:\downloads\PyWeek 8\baahtallion-0.0\run_game.py", line 29, in main.main() File "c:\downloads\PyWeek 8\baahtallion-0.0\gamelib\main.py", line 177, in main pyglet.app.run() File "C:\devel\Python25\lib\site-packages\pyglet\app\__init__.py", line 264, in run EventLoop().run() File "C:\devel\Python25\lib\site-packages\pyglet\app\win32.py", line 63, in run self._timer_func(0, 0, timer, 0) File "C:\devel\Python25\lib\site-packages\pyglet\app\win32.py", line 84, in _timer_func sleep_time = self.idle() File "C:\devel\Python25\lib\site-packages\pyglet\app\__init__.py", line 187, in idle dt = clock.tick(True) File "C:\devel\Python25\lib\site-packages\pyglet\clock.py", line 698, in tick return _default.tick(poll) File "C:\devel\Python25\lib\site-packages\pyglet\clock.py", line 317, in tick item.next_ts = self._get_soft_next_ts(ts, item.interval) File "C:\devel\Python25\lib\site-packages\pyglet\clock.py", line 585, in _get_soft_next_ts if not taken(next_ts, interval / 4): File "C:\devel\Python25\lib\site-packages\pyglet\clock.py", line 563, in taken if abs(item.next_ts - ts) <= e: TypeError: unsupported operand type(s) for -: 'NoneType' and 'float'Sounds kind of like a pyglet bug, especially as it also occurred with one other game I tested (but there it only happened once if I recall correctly -- here it happens before I even get bored of shooting things :)). Would you like me to report it in the pyglet issue tracker or do you have some idea of what may be the cause?