Welcome, new user. Please log in or register.


Additional rules

And yes! here they finally are. The rule-o-matic has decided and this is the result;

genre requirement

**** There will be 1 genre rule

genre rule #43
theme: garbage

Garbage, Debris, Filth, Junk, Refuse, Trash, Rubble, Sewage, Garbage can, Garbage Disposal, Garbage man, Garbage collection, Recycling, Land fill, Sewage pipes, ...

Artistic requirement

**** There will be 1 artistical rule

artistical rule #54
news events: use current news events


It's up to you how you involve this in your game. You can single out a particular recent event and use that as a theme in the game, or you can do something clever with several news items at once. Try to pick world news, something that all participants will be able to relate to.

technical requirements

**** There will be 2 technical rules

technical rule #61
smoke effects

technical rule #35
must use flame fx (such as in exflame.c) or explosion fx

A cool fire effect can be achieved by creating random hotspots that slowly fade and scroll up (This was quite the thing back in the days of the demo scene) There is a short tutorial here: http://www.qzx.com/pc-gpe/fire.txt. I'm sure more info can be found online. Variations of this effect that are not really fire (e.g. explosions, or some kind of magical ice fire) are allowed too, as long as the graphics are generated on the fly.

Smoke fx can be generated using some sort of particle engine, or using blending. The smoke can be combined with the fire fx rule to display a really awesome realistic bonfire, or they can be separate. Extra kudoes if you can make the smoke part of the gameplay in interesting ways.


**** There are no bonus rules

No bonus rule this year, unfortunately.

Standard rules

1. time: The competition is from Friday 30 March 2007, 12:00 UTC to Monday 2 April 2007, 12:00 UTC. You are not allowed to write code for your entry before or after these times. All entries must be submitted before Monday 2 April 2007, 12:00 GMT to an address that will be provided later (if you know in advance that you won't have an internet connection at that time, perhaps because you have internet at work and not at home, in that case you can get an exemption for this deadline. Please let me know in advance if this is the case for you).

2. size: the entry may not be larger than 400.0 KB, zipped.

3. source: the complete source code must be included with the entry. You don't have to include the source of allegro add-ons, as long as they are easily found on the web. (For a list of common add-on libraries, see the allegro.cc resource directory). And of course you don't have to include the source to Allegro.

4. code reuse Because reusing code is an essential hacking skill, You can re-use any code that:

  1. You are legally able to do so (your own, GPLed, giftware, public domain or any other Free Software licence) AND
  2. Was available and easily accessible online at least two weeks before the start of the competition This means that until two weeks before the start of the competition you may still upload your own code (e.g. initialization code, utility classes) that could come in handy during the competition.
Also, you are obliged to make clear what parts of your entry you re-used, preferably in a readme.txt that accompanies your entry.

5. Allegro & other libs. The game may make use of Allegro add-on libs or other libs as long as they are portable. The game must make use of Allegro.

6. programming language you may use any programming language that has allegro bindings.

7. portability. Your entry should be trivial to port to any platform that Allegro supports (that means including Windows, Linux and Mac OS X). This means that you are not allowed to use any OS-specific features in your game (Essentially you should aim to make your entry compile out of the box on all platforms, but this can be hard to realize for people who don't have access to those platforms).

8. additional rules. There will be additional rules that are announced at Friday 30 March 2007, 12:00. These rules come in four categories: Genre Requirements, Technical requirements, Artistic requirements and Bonus rules.

9. reviewing and deciding a winner. To ensure that each entry will be reviewed, each entrant will be assigned two entries to review and six entries to grade. Awards will be assigned based on these grades. There will be awards in the following categories:

Other Important Info

You can assume that everyone will have a copy of the latest stable Allegro library (standard installation) installed. You do not need to supply one. 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 properly 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 Email over the weekend. This does not affect your space requirement.

There will be a mailinglist for participants, where you can easily drop a message to all participants. The mailinglist will be closed a few months after the competition. Experience has taught that there are always last minute bug fixes after the competition, this mailinglist will be the place to announce them.

As always, a web-based speedhack log facility will be available during the competition.

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

Any other questions? Send mail to me and keep working! I'll get back to you as soon as I can.. :-)