In my latest commit I have made it possible to interact with an uninteresting scene. There's not much yet in terms of a game, and production value is pretty much zero. But for those curious about what it is that I'm building, you can already start having an idea. Launch the program and move right and down. Look at the map and at how the histograms update.

Now think, for a moment, about how much you'd hate if you were only allowed to look at the histograms in this game. Welcome to my game. It's horrible.

Current status of my game:

• All levels have been made.
• Animations between most levels have been created. Zooming animation to get to first level requires more calculations and moving from the 'm' at the end of 'Bitstream' to the 'M' at the beginning of 'Manipulators' has not been started.
• Graphics for nanobots requires some work.
• Animation of the game being corrupted does not exist.
• There are no instructions for how to play or what needs to be done in the game.
• User interface shows your health, the enemy nanobot's health, and the target that that character is supposed to be.
• There is no special screen for when you either win or lose.

Since my game seems to be almost done, and it is only about halfway through the week, am I allowed to make another game? I already looked in the rules, which made no mention of multiple individual entries, only saying that you can enter multiple teams. So, is having two individual entries allowed?

Starting to feel the stress now. I don't get that many hours everyday to work on the game. Most of the gameplay-code is written now. Still have a few big elements to finish before its actually playable. I think its turning out pretty nice, Id rather finish with some gameplay Im happy about then putting alot of time in the art. But I hope that the last pieces of the gameplay will be finished pretty soon and I can focus on the art and fine-tuning.

Ok, still a rather long way to go. I would like to finish the basic game-design by Wednesday night. Need to write the algorithm for the computer controlled allies and computer controlled enemies (malware, in this case). This will happen on Wednesday (which is today, hehe, because I didn't manage to write this entry yesterday). I might upload a screenshot that shows the current in-game screen later on.

Today i was a little busy but at the night i made some improvement to my game. Now my hero can shoot in the direction that he want independently where he is walking.

tomorrow i gonna work on graphics.

Finally the core of the game is up and running. I have the main gameplay loop working alongside the story.

I can see the elements coming together but there is still a lot of tuning to make it fun, and not confusing, to play. I probably have about 30% of the dialog written but I'm less concerned with that at the moment as I need to do much more on getting the core loop fun.

I found a neat way to be able to incorporate the data charts without too much programming effort and this should help the story also.

With only two days to go (for me) I'm probably about on target but it is really going to depend on how long it takes to tune things. I think I've managed my planning and energy level a bit better than in previous pyweeks so I don't feel too tired right now.

Yet another 24 hours has gone by, there's still a lot left to be done, and I really do feel like I'm falling behind.

Recently, I got new levels to unlock when the player activates data nodes in previous ones, so I'm happy about that. After I submit this diary entry, I'll start implementing keys and their corresponding locked blocks. There's other things I've done but I already forgot the specifics. I guess that's what commit logs are for. By the way, if you have time, the Git repository can be found here.

I made a level select screen in the process as well. The bare minimum that I want is a tutorial world, although it's a relatively low bar to meet. I'll definitely want to add more worlds as well as some sort of story if time permits.

I need to start implementing the portion of the gameplay where the player puts the data fragments together by the middle of Day 4, or else I might not even accomplish the bare minimum in time. I've never implemented dragging-and-dropping stuff before, and that might be a problem. I do have alternative keyboard-only mechanics in mind if I get stuck, although that'll be less satisfying to use in my opinion, but whatever works, right?

Today was definitely not very productive, but since I didn't write what I did yesterday, I can make it look productive :D

• A github repository was set (https://github.com/Freyj/Pyweek20)
• I made a sort of UI and chose some artwork (source is on the github repository)
• You can now lose the game

Didn't post much in the past 2 days so here is a status update: Github repo: https://github.com/benoxoft/Wikipedia1942 A lot of work has been done on the UI so far. Not much on the gameplay. Most sprites are animated and there is a background. Today I'll keep working on the user interface.

"Why have a simple, easy to write UI, when you can have a simple, complicated to write UI" - Me apparently So one of the key features of my game is the ability to modify the properties (i.e. data) of an object (inspirational!). So, I've made a little bar at the bottom where I'm putting little bars that let you change stuff like angle and magnitude. Of course, I could have it that you click it and it forces you to enter something in the console. But nooooo, I decided to make little slidey bars that let you change this stuff. Getting this game done in time will be a pain.