Entrants must be 1st year Full Time Undergraduate 3rd level courses.
One entry per educational institution will be allowed. Colleges and Universities must officially register their entry into the competition.
All robot submissions must arrive in electronic format no later than scheduled dates. All paperwork must be included with the submission.
Copies of entrants source code must be submitted to the Interview Panel for review, as set out in the competition schedule. The student(s) must also supply supporting documentation explaining their tanks behavior and how they have implemented this in the source code.
The Interview Panel will be nominated by the organising committee. The Interview Panel will meet with all National Final Entrants prior to their competing in the event. The Interview Panel must be satisfied as to the suitability of each entrant’s submission and that it fairly reflects the work and research of the individual or each member of a team. Each team member must be present themselves for interview.
If a team member does not present for interview then they cannot form part of a competing team, no exceptions.
We propose to use source control for submission of robots, more details will be released in the upcoming weeks,
One robot is allowed per team entry. This robot will be used for all battles.
The Robocode tank will only use the classes and methods available in the standard Robocode Development environment of at least Version 1.6.2. and the Java SE 6.0 API Specification. These are available for download from the Get Started Page. No other API’s or external classes will be allowed. The Robocode tank is “not” allowed to extend the AdvancedRobot class.
The Robocode tank should be contained in one JAVA file. This Java file can contain multiple classes. Files will be compiled prior to entering a battle match. Robots that do not compile will be disqualified from that battle / match. External configuration text files will be permitted where this has been explicitly stated in the entry documentation.
The structure for qualifying and the number of robots in each group and the match format will be agreed after by the organising committee when total number of teams entering is known. Sentry robots will be used in the qualifiers. So the battles will be of type melee, two teams and two sentry robots. The guiding principle of making it manageable, easy for the audience to follow and allowing a team to play as many battles and other teams as possible will be used when deciding on the qualifying structure.
Semi-Final and Final will be used. Battles will be of type melee and will include 2 teams and at least 2 sentry robots.
First to 7 for final
First to 7 wins for semi-Final
First to 7 for 3rd and 4th
The teams that fail to qualify for the final stage will take part in a melee battle to determine 5th to last place.
The number of rounds will be set to 5
The team with the highest score as determined by the Robocode sw will be determined to be the winner and will awarded 5th, place.
At least 3 sentry robots will be used in the melee battle, they will be WallKiller Clockwise and Anti-Clockwise. Multiple Robots of type WallKiller Clockwise and Anti-Clockwise may be used.
The screen size for all battles will be 800 x 600. Cooling gun rate will be 0.1 and inactivity time will be 450. Robots energy, name and scan arcs will be visible. Frames per second will be set at a rate that allows the audience to view all aspects of the battle. If there are a large number of robots taking part in a battle a slow frame rate e.g. 15 may be used. If there are only a small number of robots taking part a faster rate e.g. 30 will be used.
The Robocode Java code must be the creation of the contestants. Any breach of this will result in immediate disqualification. Plagiarism in the Robocode competition will be where an entrant presents java code verbatim from another source without proper acknowledgment, where they incorrectly identify the inventorship, intentionally distort code from another source and present as new material. This will also include where an entrant cannot present the material to the panel of judges during an entrant interview process.
Time will be allocated to tweak/modify the Robocode Robot between qualifying battle and the final. The time available for modifying the tank will be advised prior to the National Final. Tweaking will only be allowed for code submitted to the Interview Panel as per rule 5.
No computer readable material should be brought into the Code bunker area, all storage devices will be supplied by Tipperary Institute.
No coaching will be allowed during tweaking sessions. As per rule 6 the tank should be the work of the contestant. Computers will be provided to contestants by Tipperary Institute to facilitate the tweaking process. Use of laptops will not be permitted.
The decisions of the Organising committee, Interview Panel and Judges will be final.