name mode size
arobotsconundrum 040000
concept 040000
resources 040000
tests 040000
.gitignore 100644 0 kb
GPLv3.txt 100644 34 kb
README.txt 100644 2 kb
a-robots-conundrum 100755 3 kb
cc-by-sa-3.0.txt 100644 22 kb
setup.py 100644 0 kb
README.txt
=================== A Robot's Conundrum =================== A Robot's Conundrum is a puzzling game. It has puzzles to solve, but it's up to you to figure out how to solve them. You control a robot with the arrow keys and the space key. The code of A Robot's Conundrum is free software under the terms of the GNU General Public License version 3 (or any later version). The artwork is free culture under the terms of the Creative Commons Attribution-Share Alike 3.0 license. See the files GPLv3.txt and cc-by-sa-3.0.txt for the full license texts. A Robot's Conundrom was created by Sakse Dalum, Niels G. W. Serup, and Lasse. This is version 0.1 of the program. The development version can be fetched by running $ git clone git://hongabar.org/a-robots-conundrum The development version is probably neither active nor stable. The games' website is http://projects.hongabar.org/a-robots-conundrum (NOT UP!) Installation ============ A Robot's Conundrum depends on PyGame <http://pygame.org>. If you haven't downloaded the .tar.gz file, run % easy_install a-robots-conundrum (NOT UP!) to download and install it in one go. Else, extract the archive, cd into it, and run $ python setup.py build (NOT DONE) % python setup.py install (NOT DONE) The game can then be run like this: $ a-robots-conundrum There is no in-game menu for adjusting things; that happens on the command line. To see which things can be adjusted, run $ a-robots-conundrum --help Notes ===== Dangerous randomness in rolling boulder puzzle ---------------------------------------------- There is a puzzle about a rolling boulder in level 1. It's not guaranteed to be solvable, because you might not be able to move an arrow block to the position you need to move it to. However, this scenario is so unlikely that we have chosen to ignore it. Lack of code niceness --------------------- The code works but is a bit messy. Lack of efficiency ------------------ The code could certainly be more effective.