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 #130
Theme: Flowers - There should be different flowers in the game, the more the better!

Comments: This rule just reminds me of my favourite platformer, Super Mario World 2: Yoshi's island - it was FULL of flowers: flower enemies, flower collectables, flowers in the background, flowers that grow to form new platforms, shy guys using flowers as camouflage in the flower beds...

Artistic requirements

**** There will be 1 artistical rule

artistical rule #60
make fun of old-fashioned things. 

Comments:E.g. have a mode in which the game plays in black and white, featuring an old granny in the corner saying "I didn't pay my colour television license for this", or occasionally "I was in a war" Some more inspirations here and here

technical requirement

**** There will be 2 technical rules

technical rule #10
Your game must include procedural content. Bonus points if procedural generation is used to create the gameplay environment.

technical rule #68
some kind of special text scroller

Comments: I'll leave you with some inspirational links

bonus rule

**** There will be 1 bonus rule

bonus rule #9
Act of monkey - you may replace a single rule by a rule that has the opposite effect 

Comments: Lots of wiggle room here. For example, you could revert the last technical rule to have a non-text scroller, non-scrolling text, or simply, no text scroller.

Standard rules

1. time: The competition is from Friday 8 May 2020, 12:00 UTC to Monday 11 May 2020, 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 11 May 2020, 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 5.0 MB, 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. Use of Allegro. Contrary to previous editions the use of Allegro is not compulsory. You may use any engine, framework or programming language, as long as you take care to make your game portable (See point 7).

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 8 May 2020, 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.. :-)