Because I'm interested, as well are a number of other people reading the messages, I threw together a quick survey for the system capabilities of PyWeek participants. The PyWeek site has hosted similar things before but not having access to that I used Google Docs. :-)

So anyone who wants to can fill out the survey and/or view the results.

Every Pyweek I say to myself "This time I'm going to make a real effort to write regular diary entries, with screenshots and lots of lovely stuff about how the game is working out." Every Pyweek I fail miserably.

This time, I'm going to try something different. Instead of failing to post long in-depth pieces about how things are going, I'm just going to occasionally vent on Twitter. I'd like to invite anyone else interested in doing the same to follow me (@mewo2), and to post their Twitter IDs in this thread so that I can do likewise. I'd also suggest using the rather original #pyweek tag.

MESSAGE BEGINS

This morning we discovered that BT had (meaning to upgrade his connection) cut off one of our team members. Unfortunately he was hosting our Subversion repository. In anticipation that it might return we started working on our working copies. At 6pm we decided it was getting silly... We needed to merge.

Basically two of us (Martin and myself) were based off 1929 and JJ was based off 1927. So:

• We copied JJ's WC, reverted it and committed it to a new repository.
• We committed a reverted copy of Martin's over that bringing us to 1929.
• We brought the WC for the new repository back to the 1927 mirror and brought in changes JJ had made, updated, merged and committed 1929a.
• We brought it back to the 1929 mirror and brought in Martin's changes, updated, merged and committed 1929b.
• Once more we brought it back to 1929 mirror and brought in my changes, updated, merged and committed 1929c (aka 1930).

It was a wild time travel adventure that made all of us appreciate why we use source control...

MESSAGE ENDS

Today was very productive, especially from an interface point of view. Certainly the most satisfying thing I did today was making transitions between screens on the menu animated. Check out the menu screen (its static, trust me the animation is cool):

I have to say: I'm really pleased with what we've produced this time. I feel like it's been a very long week but we've got some excellent results. So I present to you the fourth Super Effective PyWeek production, Happy Insect Garden.

Happy Insect Garden is a bizarre style of defender game featuring:

• 19 different types of creature with flavour text as and when you find them
• 117 unlockable achievements for your completionist enjoyment
• 8 different levels, each showcasing different gameplay
• a variety of different creature movement AIs bringing it to life
• beautifully shaded graphics in a mix of rendered and vector styles
• a jaunty folk/traditional music theme to keep you entertained
• the most satisfyingly smooth menu graphics I've ever produced

To whet your appetite, just look at the following screenshots:

Then download the final version here.

To people who might have tried to play the game while I was writing this post, there was a bug that prevented the first level from being possible. Please play the current version, thank you. :-)

If you have problems with the game please tell us either below or on #pyweek (find Membury or mewo2) or by e-mailing insect-garden@supereffective.org.