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 #119
Theme: Doctors & Health

Comments: Direct intepretation of this rule should fit with a large range of games, from "Dr. Mario" to "Hospital Tycoon". But more broad interpretation is allowed too, for example, a plot where an evil mastermind with a doctorate degree is somehow concerned about his health.

Artistic requirements

**** There will be 2 artistical rules

artistical rule #87
The game shall have a pause mode where all the characters dance to a funky tune

artistical rule #83
The game must include a silly weapon or powerup.

Comments: Any sort of rhythmic movement will do for dancing. And I'll rule that the dancing doesn't have to be limited to the pause mode, you can also use it elsewhere in the game, maybe even as a game mechanic.

As for silly weapons - Worms was famous for this (exploding sheep, anyone?). Somebody even made a top 10 silliest guns video on youtube.

technical requirement

**** There will be 1 technical rule

technical rule #40
Use a morphing effect somewhere in the game.

Comments:Wikipedia explains what is meant by morphing. Dissolve, cross-fade, basically you can use any kind of technique where one image turns into another image with procedurally generated intermediate frames. Bonus points if you can make morphing part of the gameplay. For example, in Yoshi's Island, Yoshi could morph into a helicopter, a submarine or a race car.

bonus rule

**** There will be 1 bonus rule

Bonus rule #4
Act of Youtube: you can opt out of a single rule if you make a video related to your game in any way and publish it before the deadline of the competition (on whatever you like, Youtube is not a must). It could be a gameplay demonstration video, a time lapse of your code's screenshots, a video of your workplace for the game or even a video dancing like a chicken while screeching "hi, my game is good". It needs to be explicit that the video was done for this game (and not just for anything you might had done before).

Comments: Other valid options besides youtube are: twitch.tv, allegro.cc, your own website, etc. Make sure you let people know in the README of your game where to find your video.

Standard rules

1. time: The competition is from Friday 20 October 2017, 12:00 UTC to Monday 23 October 2017, 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 23 October 2017, 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. 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 20 October 2017, 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.. :-)