Current Time
October 23rd
8:18 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

    Insanity! (Good)

    Your project should either be about insanity or have a featured character who is insane.

  2. Technical requirements

    There is 1 technical requirement:

    Krakka-BOOM (Good)

    You must explode things. Preferably beasties or nasty people. Bonus points for environment interactivity (aka blow up the walls!).

  3. Artistic requirements

    There is 1 artistic requirement:

    Show some respect (Good)

    In many games, the game and characters within refer to you the exact same way whether you are a level 1 novice warrior or the dude who just saved the world.

    Avoid this in your game. Make the in-game characters notice player's actions and respond to them, or make the game itself change the way it refers to the player according to his deeds and achievements.

  4. Bonus rules

    There are 2 bonus rules:

    Act of Efficiency (Good)

    You may opt out of one other rule if the ZIP file of your entry is less than 150KB (153600 bytes)

    Act of Dog (OK)

    The Act of Dog is designed as a get-out clause for not implementing one or more of the requirements - providing that the entrant can come up with a extremely good explanation for not doing so. And when I mean good, I'm talking watertight. If I can find a way through it, then I will.

    Lame excuses will be not be accepted, and may result in public embarrassment for the entrant concerned. Successful attempts at 'social engineering' will give you a waiver. All 'Acts of Dog' must be negotiated with me via Email before the entry is submitted on Monday morning.

    Humour (of all grades) may be employed in your argument. Other techniques (underhand or otherwise) will have varying levels of success. Send all petitions to arron@ashutt.demon.co.uk with good reasons, bribes, incriminating evidence and pitiful pleading. Judgement will be as swift as the organiser sees fit.

  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.