I decided to enter PyWeek 24 just before a start, so I didn't have a time to decide what type of game I am planning to make.

The most important this was that the game has to be easy to make, because I'm Python/PyGame beginner. Initially I though about puzzle game, but it was hard to come up with good idea for gameplay. After considering a few options I decided to something simple and traditional. The core of the game will be shooting and controlling a vehicle. Although it might change during the "production process" :) Today I only managed to write a few lines of code and make a few pictures for the game. I hope tomorrow will be more productive!

I've barely used PyGame before but I have a week mostly-off from work so, hey, let's do this. I'm going to try making all my own musics and sprites to the best of my ability, but we'll see if that holds up.

So we are underway! Creating content is the hardest part with limited time. Going to experiment and try new things design wise. That's always more fun!

Day 1 has been a good day - only done a few hours but solid progress. Getting my head around Pyarcade too.

The plan is for an overhead boat game where you rescue people from the water and return them to your base. This is all a government conspiracy, of course, so the hidden budget ops trained sharks will be attacking real soon. Also some black helicopters may fly overhead...

The boat zooms about pretty well and the various debris spins and floats around. The rotation and scaling features of Pyarcade are so easy to use. The trail behing the boat is okay but I am sure it can be improved.

Everything being kept on GitHub if you wish to take a look. Sleep time!

Ever since watching stumbling upon a few videos where people hot-swap code in order to demonstrate game physics tweaking, I wanted to know how they do it. Turns out in Python it's really easy*. Just reload(module) and the magic starts happening. See some random guy demonstrating this here.

It comes with a few pitfalls, though:

• You gotta remember to import your modules, not their symbols
• You gotta make one main class as stupidly simple and as crash-resistant as you can
• To simplify swapping, you gotta work with smart modules, rather than smart classes
  

I'm like 70% through the process of making my game updateable while running, the last steps I can think about ahead of time are:

• Make the game state JSON serializable (that unfortunately means working with few classes and more modules)
  
• Add hotkeys to dump the gamestate or to reload a gamestate
• Make the game initialization initiate the game with serialized JSON data

Today is (hopefully) probably the only day in which I'm going to focus on trying to make this happen. If I end up stuck in developing this feature it's best I just dump it, as it will probably not pay off in the timespan of a week. I'm sure there's better ways to do this, but this is my first try at this. :)

My current engine model is as follows:

• Game object, which contains a basic loop, and functions to handle input, simulate and render, all which are delegated to an "engine" module, which receives the object itself as well as the game data. All of those functions are written to prevent crashes, as I might want to preserve data that was created as a result of swapped-in data. As well as a swap requester function, which causes the engine try to swap the "engine" module.
• An "engine" module, which actually handles the pygame stuff, such as initializing, polling for events, rendering stuff on the screen, as well as attempting to perform arbitrary game data upgrades upon swap.
• The "gamestate", which is a dict of primitive objects intended to be serialized in JSON and passed around to smarter modules.

If you want to look at the atrocious in-development code, see here: https://github.com/shundread/pyweek24

A good start for the first day. I'm making a clicker-RPG-fighting game and I have the design and underlying game model working. Which is good for two reasons,

1. I don't have much time this week so I need to be almost done by the end of my Sunday!

2. I realised that there are lots of variables to tune in the game so I'll have to write some kind of simulation mode to avoid having to play it hundreds of times myself!

Good luck to everyone!

I've been thinking over what to do with conspiracy theme... I arrived at the conclusion of who I'll make as culprit... Math is  gonna be the culprit...
Math is behind nearly every single thing in this world (personally, i think nearly is an understatement)... So, I'm gonna try making a  game focused on math... the game should convince the user on the fact, or at least attempt to anyway ...
Now i'm thinking over what the game should look like

Since CircuitPython is mostly compatible with Python 3, the only thing I really need to run PewPew games on a desktop computer is the pew.py library for handling the display and key presses. Turns out that PyGame is pretty much perfect for this — the code is even shorter than for original PewPew.

I have the emulator working now, available at https://github.com/pewpew-game/pewmulator and I have tested it with the two demo games for PewPew: tetris and snake: https://github.com/deshipu/pewpew/tree/master/games.

Now I can start thinking about the game itself.

Hi. I've been brainstorming and planning till now. not the theme I excepted so I was blank at the beginning. but now I have a bit of clarity, I am excited and I'm trying to manage it. experience has thought me to pace myself I hope I gain better understanding as I go. I'm really excited though dammit!!