TINS Logo

Welcome, new user. Please log in or register.

Rules

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 #79
Theme: creative anachronism: combine two elements that are obviously from different time area's

Comments: Here are a few examples:


Source: pbfcomics


source: Calvin & Hobbes


source: ChronoTrigger

Artistic requirements

**** There will be 1 artistical rule

artistical rule #56
Here be dragons

Comments: Simple enough: your game must have one or more dragons in it. The dragon may be the player character, or the final boss, or a random third-party. I'll refer to wikipedia for inspiration: Games that have dragons in them.

Technical requirement

**** There will be 3 technical rules

technical rule #42
must have way to record progress / save games

Comments: You must have some way to record the progress of the game and return a later time. You may save the game state to disk, or implement a passcode system. Some games allow you to save / reload at any time (e.g. just before a boss battle), but that ruins the challenge level of the game according to some. How you choose to deal with this issue is up to you.

technical rule #61
multilayer scrolling (=parallax scrolling)

Comments: Parallax scrolling is used to introduce a depth effect in 2-dimensional games, most popular during the 16-bit era. This animated GIF says it all:


(source: WikiPedia)

One of my favourite example is Tiny Toons from the SNES. See for example the clever use of non-overlapping strips of desert in the background. See the video from around 2:10. The smaller cactusses in the back move slower than the bigger ones in the front.

Please note that this doesn't imply that you have to do a platform game. There are plenty of other game types that could involve parallax-scrolling, such as space shooters, arcade or even puzzle games with a large enough playing board.

technical rule #64
prominent use of prime numbers

Comments: Review prime numbes on wikipedia. Anything goes, from a prime-number based puzzle game, to a background story featuring primal numbers, to a public-key encryption algorithm based on primes.

Bonus rules

**** There will be 1 bonus rule

bonus rule #9
Act of Guttenberg - swap a rule for a rule of an earlier competition,
if you re-use code from an entry from that competition (not your own). 
You can apply this rule several times if you re-use code from several entries.

Comments: This is a very powerful bonus rule, but it is also a challenge to implement. To apply this rule successfully, you must re-use a significant chunk of code from a previous TINS or Speedhack entry that you didn't write yourself. Extra points if you manage to make the re-use obvious, e.g. if you manage to re-use a feature from the earlier entry that is instantly recognizable. If you do so, you may choose a replacement rule from the competition that this entry is from. The re-used code does not have to be related to the replacement rule. For example, you could re-use the coordinate tranformation code from Shawn Hargreaves' 1999 entry "SPEED" (which should be instantly recognizable), and choose "Use the number 29" from Speedhack 1999 as a replacement rule.

And, as said before, you may apply this rule several times, as long as you re-use code from multiple distinct entries (that aren't written by you)

Carefully document which snippets of code you re-used, and which replacement rules you chose, in an accompanying README.txt.

Standard rules

1. time: The competition is from Friday 3 August 2012, 12:00 UTC to Monday 6 August 2012, 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 6 August 2012, 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 3 August 2012, 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.. :-)