Breach: Post-Pyweek notes

Thanks for your comments on my game! I'm glad that you enjoyed it. :)

I've already discussed the game in my previous post, so I don't have much to say that I haven't said in it. I just want to comment on the "PS" portion in my previous post, because it's an interesting tidbit on the story of the development of the game.

I asked in that post whether there was a way to compute any boolean function with a level in my game (in theory). The answer is yes. The game has NOT gates, and doors behave in an OR fashion: it requires at least one wire to be on in order for it to be closed. Now, a NOR gate is an universal gate, meaning that we can construct all other ones from it, so if we can make one of those, then we're done. A door is not exactly able to produce output, but the feature I added in later levels does allow you to retrieve the output of a door: with track-powered sources, we can position a track, a door, and a source, so that the source is on if and only if the door is closed. This plus attaching a NOT gives us a NOR gate, which we can use to construct any other gate and therefore compute any boolean function.

In fact: this was what drove me to make a crucial decision late in the week. I was originally going to add AND and OR gates to be used just like the NOT gates. The reason is that having only the NOT gates limits the depth of the puzzle a bit. However, I liked the simplicity of having just one type of gate. So I thought, could I do something else that gives me the power of AND/OR gates, and yet lets me maintain this simplicity? For example, I had drawn a use case of AND gates where you had to keep a wire on in order to close a door behind you and avoid a track escaping. Well, in the second to last level, something similar is executed in the top right part of the level -- yet not with an explicit AND gate. The thing is, I realized that doors worked as an OR, but there was no way to capture their output. So I came up with the idea of track-powered sources, which emulated that and fit pretty well with the whole game. It just felt right: while you have to manage doors in order to take care of tracks, this feature made it so you also have to manage tracks in order to take care of doors, and we get a nice circular relationship going on. Time constraints only allowed me to make the 4 levels with track-powered sources in the game, but I think you can make some neat stuff. As a bonus, that was easier to implement than AND/OR gates. :)

Anyway, congratulations to the team winners, and thanks to blakeohare for hosting this Pyweek! See you all next time! (Also, xmzhang1, thanks for that cool award picture. :))

(log in to comment)


How can I make the game work with Python 3, I get the following error:
$ python3 
Traceback (most recent call last):
  File "", line 3, in 
    from gamelib import main
  File "/home/jorge/Descargas/Breach-1.0/gamelib/", line 11, in 
    import game
ImportError: No module named 'game'
I am so glad that you like it! I was really shocked when I knew you have joined pyweek for 20 times, that means least ten years! Well, I prepared a awesome picture for your 100th, do you want to see it? ^ v ^ I'm just kidding, forget about it. You are always the pyweek legend in my eyes!
Congrats on winning and on your 20th pyweek! Ten years of service is amazing :) I really, really liked the puzzle design in this game ... it was very elegant: complexity that manifests out of simple rules.

@jorgesumle: The game supports Python

@jorgesumle: The game supports Python

Huh. Some bug happened when I posted my comment. :/ I guess it didn't like the less-or-equal sign. I'll rewrite it and repost it.

@jorgesumle: The game supports Python 2.7 only. Sorry. :/ There's a Windows py2exe'd version if that's helpful. (I forgot to mark it as final, but it's there.)

@xmzhang1: Thanks! I was just lucky to catch Pyweek at its beginning, and time flies. And yet every time I'm amazed by what people can do in one week. :)

@mit-mit: Thanks! I'm glad you found it elegant: that's what I was aiming for. It's just so fascinating to see depth coming from simple mechanics in games, and I wanted to give a shot at it. I was very impressed by your game, too. Polishing a game to the level that you did is something I have yet to learn.