Current Time
October 26th
5:52 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

    Fantastically Mundane (Great)

    Take a boring, everyday activity and make it AWESOME.

    Examples: Broomstick Avenger, Shave or Die, Commute 2: Commute Harder

  2. Technical requirements

    There are 2 technical requirements:

    Character Development (Great)

    The game should feature some form of character development, like gaining experience points, leveling up, increasing stats... etc.

    Go Procedural! (Excellent)

    Some element of your game must be generated procedurally. Good candidates for procedural generation are levels, graphics or sound effects.

    Extra kudos if all elements of your game are generated procedurally.

  3. Artistic requirements

    There are 2 artistic requirements:

    Foot of the Hedgehog (Great)

    Sonic tapped his foot impatiently. Mario fell asleep and dreamed of pasta. Your game, too, must do something cool or unexpected after being left in "idle mode" for a certain period of time.

    Toon Violence (OK)

    Feature cartoonish effects like getting flattened by a giant hammer or falling form a cliff.

  4. Bonus rules

    There is 1 bonus rule:

    Act of Illuminati (Good)

    You may opt out of one other rule if you include a picture of yourself accessible via some secret within the game itself. This may be a secret area, key combination, menu item, etc. Instructions on how to unlock the secret must be hidden within your documentation file in any way you deem fit, as long as it is realistically decipherable.

  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.