Current Time
March 30th
9:47 PM UTC



Log In


Compo:


SpeedHack

Rule-O-Matic

Rule-O-Matic

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

    Wind (Great)

    The game must incorporate wind as a key element of the gameplay.

  2. Technical requirements

    There is 1 technical requirement:

    Rope Physics (OK)

    swinging ropes, bungi cords and grappling hooks all count.

  3. Artistic requirements

    There is 1 artistic requirement:

    Save a Princess (Good)

    Everywhere, there is a princess to be saved. Somewhere, somehow there's one in your game.

  4. Bonus rules

    There are 2 bonus rules:

    Act of Act of Recursiveness (Good)

    Clever use of recursiveness will give bonus. It could be a code thing or something in the graphics. It could even be the way you interprete a rule. If one rule says you have to save a princess, you could make a game where a princess has to save a princess.

    Act of Punk (OK)

    Instead of following all the rules, you can break all of them! You need to do your best NOT to meet any of the requirements (of course standard rules still apply, like the size and time limit). For example, if a rule says your game needs to be inspired by outer space, your game can not FEATURE anything related to outer space, and not just not be inspired by outer space.

  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.