Current Time
March 29th
6:20 PM UTC

Log In





Don't read too much into the results of these sample spins! The method of picking rules is yet to be tweaked to its full potential, and until a good selection of rules have been added, it's rather meaningless.

Once the Rule-O-Matic has been spun for a final time, the authors of the selected rules will be contacted in order to add clarifications and last minute twists. They won't be allowed to do anything drastic, and to limit their advantage of a heads up, they won't know for sure which of the rules atually were selected. (For example, they may be notified that one of three specific rules have been selected.)

Here is a sample spin, with the following rules being chosen:

  1. Genre requirements

    A funny thing happened... (Good)

    Remember that time you went to the corner store to buy a bottle of your favourite cola, but the list of ingredients the company used had been stolen by an evil warlock and you had to travel across a hostile magical land to retrieve the recipe from his warlocky clutches?

    Start with a real situation from your life, add a twist, and play it out in game form. You're the protagonist.

    Of course, this doesn't have to restrict the genre; this could easily be anything from a puzzle game to a brawler.

  2. Technical requirements

    There is 1 technical requirement:

    Murphy, who? (Good)

    The game should apply Murphy's law in some way or another. Be it by story line, or by the player losing whenever he decides on using his luck, etc... Its all up to you!

    The more creative the use, the better.

  3. Artistic requirements

    There is 1 artistic requirement:

    In Soviet Russia... (Great)

    Take a normal relationship between two things and turn it on its head.

    For example: In Soviet Russia, car drives you!

  4. Bonus rules

    There is 1 bonus rule:

    Schizophrenic Levels (Good)

    You may forgo one artistic requirement if the area of game play (ex: the levels, the map, the planet, etc) change randomly over time during play UNRELATED TO the actions of the player(s), or ingame events.

  5. Other Important Info

    All entries must comply with all requirements except where nullified by Act of Dog.

    All entries must be submitted on or before 12:00 UTC on Monday 25th July without fail. All entries must be supplied in a ZIP file equal to or less than 250 KB in size. All source code, makefiles, documentation, and references to additional libraries used must be supplied in the ZIP file.

    You can assume that everyone will have a copy of Allegro (standard installation) installed. You do not need to supply one. It is okay to use a more recent version of Allegro, but if someone is unable to compile your game because of that, it's your fault. You should consider uploading binaries for people who have problems compiling the source onto your own website. I will be checking that the binary and source match up, so adding enhancements to the 'competition binary' is not permitted..

    If source code is reused from legal sources (your own, GPLed, public domain) you should declare this and what changes have been made, so that your work can be assessed for the voting.

    People should keep a informative and interesting account of their development through the competition. This can be sent after the competition for those people with no Internet access over the weekend. This does not affect your space requirement.

    A web-based "blog" update page will be available. This will allow spectators to see what is going on :-)

    You can make use of all information sources, mailing lists as you see fit. This is not an exam! :-)

SpeedHack created by Arron Shutt.
1999-2003 logos by Arron Shutt. 2004-2007 logos by Johan Peitz. 2009 logo by Pedro Gontijo. 2011 logo by Mark Oates.
Copyright ©2004-2011 by Matthew Leverton.