| TinyRadio |
| Silicon |
|
Grand Master
Group: Moderators
Posts: 206 (1 robots)
Member No.: 44
Joined: 20-August 03
|
|
Entry Cutoff |
April 4 2004, 10:00 PM (eastern standard) |
|
Results By |
April 5 2004, 10:00 PM (eastern standard) |
|
Send Robots |
|
|
Website |
|
|
Description |
- The contest will be run on RB v1.4.0.03, unless a new version comes out prior to one week before the contest deadline. If a new version comes out within that one week, and there is signifigant reason to use that version, a notification will be made (both on the Registry, and with individual emails to all authors who had already submitted thier bots), and the deadline will be pushed back another week.
- Teams will be disabled (this is to keep with the original premise -- to promote inventive use of radio, and to allow radio attacks)
- 1.4x turnloss
- Fast missles
- Decelerated stops
- Arena: 500x500
- Radar/Missle range: Infinite
- Radio on
- Sliding on
- Additive rotation on
- Random positions
- Random headings
- Errors will be automagically killed, so please debug your bots.
- 2048 games per match, 2v2 (teams are disabled, so the bots are chosen by the auther(s))
- All bots must use both Author() and Name(). Version() is optional.
- Points will be weighted by robot code size based on the following expression: points^2/(size*log2(size)). Size will be a sum of both bots on the team. Exempted from the size calculations:
- Whitespace at the begining or end of lines (for readability)
- Comment lines (for documentation)
- The Name(), Author(), and Version() lines
- Authors may submit up to two (2) teams. If you submit only one (1) team, that team will NOT be entered twice.
- A bot can be on more than one team. Please specify.
- Collaberation is allowed and encouraged. Both bots may be submitted seperatly, or at once, but should contain proper Author() lines.
- All teams will be matched against all other teams. Final score will be weighted and used in ranking.
- Submitted code must be in readable (i.e. not scrambled) form
I decided that teams will continue to be disabled, in keeping with the original premise. Radio will not be enforced, but not using it is likely to put your robots at a disadvantage. Remember: if you need to use some extra bytes for radio to make your robot preform better, chances are that the extra score from it being a better bot will probably outweigh the extra size.
I also set into stone the kind of tournament that is run -- I figure that having two different formats could possibly degrade the contest and the entries for that contest. The choice was made for the first option to simplify both your lives and mine.
Prior to a week before the contest, I will allow authors to request 1v1 scrimages to be run on my system. If a scrimage is requested, the authors of both teams must aggree to it. The reasoning behind me allowing scrimages on my system is to allow confidentiality of code and strategey prior to the contest.
The contest will be run April 5th. Unless I get more than 15 entries, the contest will be run in a single night. Entries will be due April 4th, at Midnight EST.
When submitting an entry, please send an email to with the subject "TinyRadio Submission". Please attach the robot(s) to the email, and specifiy in the body: a team name, and how the robot should be paired. If you make changes to a robot and re-submit, please tell me how the robot should replace previous entries (i.e. which robot(s) to replace on which team(s)). |
|
TinyRadio
