Finally got the game all finished and wrapped up at about 6:45am after a marathon night pretty much non-stop from about 8pm. I'm pretty happy with the final result: there are one or two niggly graphical bugs I couldn't rectify before release, but nothing major.

Spent most of Day 7 implementing about 60% of the game levels and puzzles: the results are OK, but I was hoping to implement a bit more variety, but just did have enough time. I'm happy with the overall feel of the game.

Play through video of the game now available (Warning: Spoilers!):

https://www.youtube.com/watch?v=zxXKugd5VZQ&feature=youtu.be

Don't have access to a windows machine at this moment, so hoping to build an exe release tomorrow, but probably won't get it done until after the deadline.

I forgot to say, you can toggle fullscreen with Alt-Enter. It's nicer to play big!

I decided to go with another puzzle game. Designing puzzle mechanics is always fun to do. :)

Designing levels was quite tricky and I didn't allocate a lot of time to it. Hopefully the levels I made should give a feel for the puzzle mechanic. The puzzle has some interesting properties, but I'm not sure if it is possible to go much deeper with the mechanics as implemented; or at least, creating deeper levels is not straightforward. The synchronization aspect of the puzzle is a bit tricky to handle from a level design standpoint.

I hope you enjoy it!

So at the end of our game, there is a song that plays but apparently, if you press space too fast, it doesn’t play. So if you don’t hear it when the circle doge goes to the middle of the screen, just go in assets/music/Last_Hi.mp3 and play it. Thank you for reading

https://github.com/ozcer/Warpin-Walter

Diary entry in readme^

Our first game. Have fun :)

There is a README.md and README.txt each with the same markdown content. There you'll find:

• Project and technical details.
• A game guide with a few tips for a more enjoyable play session.
• An explanation of the game concept.
• And trivia filling in the details of some of the glossed over references from our hero's in-game banter.

Come visit us in IRC. :)

Wow, what a rush. The last day is always super long, but you can get tons done on the back of an engine that you spent the rest of the week writing.

This morning one of the big tasks was to get the dark world looking right. It now has 3D walls, though due to some problems with the asset packs I was using there are some glitches in the way the tiles match up. I tried turning on shadows for the point lights, which looks great:

...but the performance wasn't good enough so I turned it off again.

Here's the final count on Python vs Javascript:

$ wc -l darkworld/*.py
  ...
 2436 total

$ wc -l assets/js/dark-world.js 
1064 assets/js/dark-world.js

The game logic really started to dominate once the client was capable of loading and rendering models. More and more it was the interactions that were being coded and all of that is in Python. In fact there are quite a few things to do. One of the things you can do is shop with the blacksmith:

When I made the AI a bit better, the Dark World became pretty challenging, so I don't recommend going in individually.

I learned quite a lot this Pyweek:

• Using an existing asset pack is a huge time saver for 3D stuff. I could never have got so far if I had to model everything myself. I made 10 models myself, 2 of which were animated. The rest came from asset packs, and other free model sites.
• An existing 3D engine with a feature-complete model loader is a must. Coding these things is not a Pyweek activity, and in the weeks when I've tried it the gameplay really suffered.
• Having a REPL into your engine is amazing. Every game engine should do this.
• I tried out some more modern Javascript and quite liked it.