Current Time
November 25th
11:22 AM 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

    Post-apocalyptic (Good)

    The game must take place in a world that has recently suffered a terrible disaster, whether it'll be World War III or something completely different.

  2. Technical requirements

    There are 2 technical requirements:

    Dual input required (OK)

    Game must have both keyboard and mouse control. Such as moving around with the keyboard while aiming with the mouse.

    Contra (OK)

    The game must feature a hard to beat boss at the end of every level. And a helicopter at the end of the game. (For no reason.)

  3. Artistic requirements

    There are 2 artistic requirements:

    Synaesthesia (Good)

    Synaesthesia is a rare condition where two or more senses are connected. For example, movements may have sounds, or a sound may have a twisted, colorful shape.

    The game must simulate synaesthesia to the player view point. What senses and how they mixes up together is up to you. Possible examples are enemy attacks shows illusionary shapes, or a sound may materialize on screen. Creativity is the limit.

    For quick reference, synaesthesia may envolve: vision, smells, tact, sounds, emotions, names, characters, motion, genders, shapes, and so on.

    Time Trouble Take A (Good)

    Time should somehow change throughout the game. This could either be something simple such as stopping time, or as complex as time speeding up, slowing down, or even going backwards as you play the game.

    For Time Trouble Take A, the character has no control over the changes in time, that is, the setting, or some antogonist is controlling time and you have to win despite this set back.

  4. Bonus rules

    There is 1 bonus rule:

    Lesser Act of Chameleon (Great)

    You may change one word in one rule. The result must make sense.

  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.