I don't feel like I've gotten much done, but I've thought a lot and I'm confident that we'll make some progress shortly.

I'm going to be working on a Resource Editor, then move on to a Level Editor.

While I'm mucking about with the utilities, Skaro will be engineering us a game engine. Once those tasks are finished, we'll figure out where we are and where we need to go.

My current task is figuring out pgu. Always picking new libs to learn at crunch time.

Going to go with codename AHDN, at least for now. It resembles a game I wanted to make, anyway, so it's worth screwing around with.

I drew a bunny that could disappear into a hat, but I still don't know what I want to do.

'The Disappearing Act' could refer to any game where getting rid of all your tokens first is the goal. Online backgammon?

I was hoping it to be a team entry, but... Anyway, the choice of theme (desapearing act) seams to be a difficult one. Hope I can come to some ideas soon. Some I´ve already had probably would need 3D, which could be hard for 1 week...

i have one history idea: you are a guy trying to dissapear of your wedding. i have two games ideas with this story: 1) your bride is tryin to catch you, as you run, you must avoid obstacles as well, at some time running (crossing a finishline) you can dissappear and pass the level, the mother-in-law can rush you too, i see later. 2) some kind of puzzle, you must collect some items, those give you the dissapearing ability as you avoid your bride/mother-in-law, until you completely dissapear, with various levels. 3)a mix between the 2 mentioned ideas

I spent most of the first 12 hours of the challenge working through collision detection and response. This is something I always waste that sort of time on, unfortunately. I tried a few approaches, all of which were complicated and had me trying to figure out how the innards of the pyeuclid module worked.

In the end, I retired at 11:00pm and read a book in bed. I'd resolved to try PyODE, but I knew that would probably cause more pain that it was worth.

This morning when I woke up after a good night's sleep, I had the solution. It was simple and after sitting down for about half an hour it was coded. Half an hour later it was debugged ("if you write code as cleverly as you can, then by definition you can't debug it"). Now my rabbit is bounded by fences. It can dig holes. If it digs for long enough, it goes into the hole and moves around under the ground, only to pop up elsewhere (leaving another hole).

Codename Dikkens: A retro approach to a mystery story

I must have miscounted - the contest started 24 hours earlier than I expected. Nuts.

Fortunately, I've got three separate game ideas that I've been toying with under this heading:

• Codename AHDN - realtime squad action game
• Codename Noir Room - puzzle based room mystery
• Codename Crop Circle - Haven't figured out a mechanic for this yet.

So the contest started yesterday (Sat) at 5pm for me. Now its Sunday afternoon, I slept on it, and I am still not entirely sure on which idea I am going to stick with.

I was sketching up some thoughts, and I've got Ninja Training, Hack & Disappear, and a cool Snipe/Find Items that I got the main character drawn up for.

Ninja Training - You're a ninja in training who has to get through various rigorous training exercises, until you finally have to learn to truly disappear.

Hack & Dissapear - a gauntlet style open up a box, avoid and destroy the robots that are coming after you, get the required data files, and leave through the exit.

Snipe/Find Items - you have different levels in a building, and you must hide while sniping enemies. You collect certain items from sniping certain enemies, but you have to avoid getting detected after firing!

I still have more ideas floating around, but "Disappearing Act" is a bizarre theme that I was not expecting.