VROOM41-multifac19-2014-10-FINAL-v1.1.zip is tested and compatible with Python 2.6, 2.7, and 3.2 (assuming 3.4). Thanks to DR0ID for the conversion.

What our team learned last week is that working with hexagon maps is hard! We spent a lot of time weeding out bugs that were caused by rounding errors and errors caused by coordinate transformations. Using pygame also brought its own limitations as we had to be very careful about how many blits were made ver frame and how to correctly handle hexagonal overlapping sprites. In the end, we only had about 1 day to really focus on making maps and implementing enemy behaviour, so there are only a few maps, and the enemies don't do much.

We did however accomplish a few fun things. The hexagon map display is fully 'dirty rect' compatible and renders quickly, even at 1280x800. It supports mixed column sizes, collisions, and even draws all columns over sprites. There is a built in maze generator and point-and-click map editor that saves and loads to JSON. We have a simple event system using a python dictionary, a fast simple physics systems with friction and gravity, and we've leveraged the fysom module for implementing enemy AI.

This was our first collaborative game making effort and we are planning on joining next pyweek. Next pyweek we will devote more time to planning before we start coding and set a timeline so that we don't get bottlenecked by a feature that is taking too long to implement.

After concerns we needed too much art we scaled back on the artistic goals of the game... and then work and life happened.
Basically spent more time at work than I wanted and just didn't have it in me to code anymore.
Even though I know I could get the code part of it done, I would have had to pull a couple overnighters and with work requiring that already, that was not to be.

Some entries look amazing though - so definitely looking forward to trying them!

Hi Here is a version that also runs with python 3.4. Youl will have to download it yourself from here: https://bitbucket.org/dr0id/pyweek-games/src/0700e88a606b/pyweek19-2014-10/?at=default

First thing; there's hints in the readme, in the style of Infocom's old InvisiClues. Second thing; this thing is meant to work with Python 3.4, and requires Pygame and Pygcurse. Pygame you probably already have, and Pygcurse is on pip, so you should be fine.

Here's a sample gameplay video for our game. http://youtu.be/vKA-OCNmI28

Although neither one of us were able to take the week off, this was possibly the most fun Pyweek ever. I was a bit worried midweek that our goals were too ambitious. Thursday evening the project finally started coming together and looking like we'd make it, and it was going turn out fun. Today we put the final glue in place, tested and tuned, even worked in a major feature. Many times during the week I laughed out loud at the silly fun of this game.

IRC quote of the week: ***DR0ID_ hates the cutters

I have to agree, they are the worst. And he made 'em. We should take a vote. :)

Gumm

I made a video showing the gameplay for Unvisible. It is probably a bit easier to watch this than it is to read through the instructions!

Click on the link or the image below: https://www.youtube.com/watch?v=MPm_-EgFPPo

We finally got around to naming this thing. I got some backgrounds & cards done, and took a whack at the music/sound effects today. Mike's polishing up the characters and animations; assertivist is putting the final touches on the game (while we're still technically able to upload). There's never enough time.

Hopefully we'll get a playable version up for everyone soon. :)

The Forgotten Angel, version 1

I was far too ambitious with the scope and I didn't get going until really late. If you play it through you'll see lots of rough spots where I simply ran out of time. I feel like my usual attention to detail is really lacking here.

I did, however, have a first-timer on board for the music, marybee, and I think she did a great job.

If you run into any issues running the game before the submission deadline, let me know here and I'll try to get a fix in. Thanks!