well, I fell a bit behind yesterday through lack of motivation :/

But we made up some ground today, bjorn got back earlier, and we hit the code pretty hard :)

No new screenies, but tomorrow should see some new tiles, buildings and units moving around, as well as some music implemented, and the start of the in-game gui :D

Another day like this and we'll be back on schedule.
Time for some sleep though now :)

I have expended most of the time of these two first days planning my game design. The name for my game will be "Twist'em All!". It's going to be a platformer-shooter. This afternoon I started with the code. I've already made most of the main character behavior. I'm using temporary artwork, eventually, I'm going to change it. If I have time I'm going to make my own artwork, if not, I will borrow some creative commons stuff. Time is running!!

I have known about PyWeek for a few years, but this is the first time I have decided to participate. Although I have experience with C++ programming, this is the first larger scale Python project that I am attempting.

My first day began on Monday, so I missed a full days worth of work. However, today I was able to accomplish a fair amount. I have the start of a basic PyGame/pyOpenGL game engine.

There may already exist an OpenGL based game library, but I decided to try to bang out the basics of what I need.

At the moment the program can:

• Create the window
• Load and manage textures
• Animate and draw sprites
• Use a simple scene node hierarchy for rotating, translating, and managing child objects

Tomorrow I plan on working on the following:

• Object/Object collision detection
• Object/bitmask collision
• Collision with rotating bitmasks (actually, it will be implemented so that the bitmask will stay stationary while the gravity vector rotates)
• Creating surface normals from bitmasks (these may be precompiled into an array)

Some future work that needs to be done includes:

• Parsing XML based levels
• Player controls
• An object interaction system
• Menus and displays
• Sound and Music

here's a youtube link. I made a video from our game so far, enjoy... LINK

Ok, we started at monday but I think we'll do it. We'll finish our game before deadline and it won't sucks :)

Some of us have never use pygame, some others have even never use python, anyway: We are having fun!

Next post: a screenshot of our Twisted Zombies!

I can't sleep. Why? I don't know! But what i do know is that i will not be able to finish this game with all the work load alone. not this week at least.

So what to do? Abandon my holy quest? Not me! The hours I have been laying on my bed trying to sleep has not been in vain. I come up with a new game idea. This one don't need any heavy collision detection, which was the problem with my old one.

The new game name gonna be "Twist'n Boost", a race game in a tunnel which you almost not fit into which is twisting a lot. You control the rotation of the craft and the angel between its wings/wheels. When you think you can handle it use the boost to win some time. The boost maybe will reward in some other way to in the end ver.

Another near-complete waste of a day... laid out skeleton classes for later implementation, but not a damn thing else. Living under a constant cloud of fear thanks to the news, and have a wedding to plan besides, neither of which is a Good Thing for a programming contest, especially a short term one like this.

Enough with the excuses, right? People are laboring under worse handicaps than mine, and I deserve only scorn and humiliation (and rum. Lots of rum).

Goal for Tomorrow: Implement a class, any class. Secondary objective is a rough implementation of All classes. They should fall like dominoes once I get going (har de har har).

Well, the second day of PyWeek is over (for me, at last) and I have a barely working prototype; here's the obligatory screenshot:

The game is called Galvinball! and the rules are simple: you play against the computer and whoever reaches the ball first wins. But! This is a game inspired by the famous Calvinball, so you can make rules as you play. Just write WHOEVER IS CLOSE TO TREE FLIES and it'll happen!

I created a small DSL that parses rules, splitting them in "targets" (WHOEVER IS, EVERYONE, etc.), "filters" (CLOSE TO *, FAR FROM *, OVER *, TOUCHING *) and "actions" (FLIES, WALKS OVER WATER, MOVE FAST/SLOW, etc.) and applying them to the objects in the game. Actually the game starts with the simple rule WHOEVER IS OVER BALL WINS, and new rules can be added at anytime.

The core functionality of the game is very simple: a random map with trees, water, walls, etc. The fun comes from exteding the DSL to allow rules like ALL TREES CLOSE TO PLAYER MOVE or WHOEVER IS CLOSE TO TREE DESTROY WALLS.

I am finding python weird compared to ruby but I been doing only Ruby for so long. It is the only language I know.
But still, I did some work on my Twisted Shootout game. I got some vague idea on how to do twisting landscape.
I waste too much time today. I won't be able to finish the game at this rate.

I've just finished Twisted Life 0.6.0 and it's available for download.