Your entries in the 25th Clash of the Tin Cans tournament are due by a date yet to be determined (probably in '07)
!!The previous season's (tourney 1 - 20) entries will not be automatically entered!!
24th CTC Tournament Prize!!! The winner of this tournament received 2 genuine Colour Roboforge posters: Srikar and Volker posters - 28cm x 40cm (10" x 16")
Send your entries to markus69 [at] orcon [dot] net [dot] nz and please read the rules below to re-familiarize youself with them.
Please note, the 20th tournament (#20 - 28th Sept 2003) is still in Mr Ekshin's harddrive (hopefully) and is yet to be run due to the joy that is the Bbot.Finalize() memory leak.
click here for Results of the 10/12/2006 battle
Previous results can be found at the bottom of this page
Gladiator Construction Specifications
The tournament runner reserves the right to make summary judgments concerning the eligibility of entrants. The goal is to include as many types of bots as possible, while keeping "spoiler bots" out that may be obviously designed to skirt the spirit of the gladiator games. I just don't want a situation where 9 people are unhappy because a 10th decides to enter a stick, spinner, or hammer and ruin everything.
Cost
Bots may not initially cost more than 40000 credits. Their cost of tournament winners may NEVER exceed 43000 credits.
Bots that win 3 tournaments ascend to the Hall of Old, Fat, Lazy Gladiators, and will no longer be eligible for tournaments.
Overall Design
Bots must have two arms, and two legs. The arms must be separated from the torso by at least one shoulder joint.
Weapons may ONLY be on the arms.
If there is a waist joint, the torso may not rotate more that 180 degrees total range on the chassis.
No bot may be over 5 meters tall, measured when standing still.
Size Limits
The REACH of the bot may not exceed it's height. There is a .5 meter margin of "slop" to this limit, to help when specifications get close.
NO reach may ever exceed 5 meters. The .5 meter slop rule is NOT going to allow Reach to exceed 5 meters.
Legs
Bots must have at least two legs.
If a hover chassis is used, then "Stem" parts may not be used in leg construction. All bots must have parts to represent the feet. Please refer to the lower "List 1" for a listing of parts that are considered "Stems".
Head
Bots must have a head; either the controller, or another part. IF the head isn't a controller, it must be a part that contains or supports all controllers OR sensors.
The head must remain above the highest joint in the highest shoulder joint group. Of course it may be armored. Here is a thorough breakdown of the head rules:
All gladiator bots will be required to have a head.
The placement of all controllers OR all sensors will have to be in, or attached to the head part.
The head may not be lower than the highest joint in the highest shoulder joint group. This height rule also applies to all controllers OR all sensors mounted inside, or attached to the head.
The head may be a controller.
The head my also be a standard component, joint, or energy. If so, either all controllers OR all sensors must be inside, or mounted to the head part.
The head may not be a shield, but may have shielding attached to, through, or covering it.
The head may not be solely a sensor.
The head must be mounted ON, OVER, or ABOVE the torso. It may not be mounted in a way that has it sticking beyond the cross-section of the torso. (example: Looking straight down onto the bot from above, the head should be over the torso, not beyond the torso's edges)
Part placement
The following parts may not be mounted on the arms: Controllers, Energy modules, Sensors.
The following parts may not be "buried" inside the actual chassis: Controllers, Energy modules, Sensors.
Joints
Joints MAY be stacked. They may spin as much as desired, but they may not be balanced or counter-balanced.
The torso joint is an exception to the counter-balance rule, since bi-radial construction is the nature of a humanoid form. Therefore the torso may not rotate more than 180 degrees.
Pass-Through
Bots may not deliberately use Pass-Through (also known as "PT"). This means that moving parts may not pass through non-moving ones. The simplest way to check is this: Go to the "Moves" screen. Test all joints by moving them to their limits. If at any time, something glows RED, then pass-through exists. Make sure that the moves do not make use of this.
Running and Survival
Bots may not run away while they are ahead on points, and still have weapons with which to fight in the manner that they are designed. Any bot that does so forfeits the match. The remaining bot will be considered to have received a "Points Win".
Bot may run when if they have lost their offensive capability (their weapons) and/or if they are losing on points, and don't wish to be completely destroyed.
Multi-connected construction
Bots MAY use the construction technique known as multiconnect (also known as "MC") without limitations.
List 1. Parts considered "Stems"
Cytol: Stretch, Reach.
Oratha: End, Stem.
Raiken: Half.
Srikar: Sectlimb.
Standard: Extension, Long Connector.
Ultair: Calamus.
Volker: Saw Arm.
FAQ
Q) How do I find out the height and reach of my bot? A) Select a different bot and load it into the workshop. Pick one that has good sensors and a fast controller. Smarty Pants Ned (downloadable from this site) is a good test bot. Run a test battle vs your bot with unknown reach. During the match, observe Ned's World Variables for "Enemy Reach" and "Enemy Height". *Note, For the purposes of the reach determination, the length of the arms is not counted toward bot height at any time. By doing this, you will be able to get an idea about the actual measured dimensions of your bot.
Q) How much energy is enough? A) Humanoids use a LOT of energy. Only one energy supply is NOT ENOUGH. Running out of energy leads to death in the arena. Test your bot at home, and DON'T "analyze" it. This should give you a good representation of how it will perform in the arena. If it runs out of energy, then redesign and put more on.
Them Proceedingz
The tournament will be a double-elimination pyramid ladder - or "Tree". Bots will be randomly seeded into the first elimination tree. A second bot by a designer will be seeded randomly into the second half of the tree, so that a designer won't have to fight his own winning bots until the end.
Bots that survive a loss in a first elimination match are seeded randomly into a second elimination tree. Once again, a second bot by a designer will be seeded into the second half of the tree if possible.
A house bot (Gladiator Ned) will be used to fill in the remaining slots to make an even tree. Points will be scored for beating ned in standard fashion. *Ned is will not attack, but is extremely tough. It's been found to be very rare for someone to get more than a 1 point win against him. A bot would really have to work hard to get more.*
Since changing the starting can effect the outcome of the match, there will be special attention paid to which bot will be in the #1 position (Pole position).
After the first elimination tree is randomly seeded for round 1, the bot that is first in the list (out of a two-bot match) has pole position.
During all subsequent matches in the first elimination tree, The "pole position" bot will be randomly drawn before each fight.
The pole position for round 1 of the second elimination tree works the same as in the first elimination tree, as does the position selection for each subsequent second elimination tree fight.
The pole position for the final match will also be randomly drawn.
The winner of the first elimination ladder will fight the winner of the second elimination ladder in a "wildcard match". This is the final gladiator vs gladiator match.
Bots that lose by "Controller Kill" or "Chassis Kill" are completely out of the tournament at that point.
Points will be awarded during the matches on the following basis. Also note that special overall points will be awarded for designers who make an effort to enter bots that increase the spirit and entertainment value of the games:
One point for a win based on points.
Two points for victory by controller kill.
Three points for victory by Chassis kill.
(Style win) Four points for successful use of "missus" (points victory, yet sparing the enemy if their energy is destroyed.) This would entail ceasing hostilities and moving to the center of the arena. Also a great time to have your bot cheer to the crowd.
Four points for winning the final "Wildcard" match, regardless of means.
One overall tournament point awarded for the effort to paint a discernable "face" on the front of a discernable "head".
One overall tournament point awarded for taking the time to include "start" and "victory" moves.
No points are awarded for matches fought in the second elimination round, unless the bot wins the wildcard final match.
The finals winner will have one last bonus match vs a horrible, overpriced beast bot. Standard scoring will be used. A bot that loses to the beast simply gets no points, but is still the tournament winner. Though if it loses, other bots will tend to point at it and laugh as it leaves the arena.
At the end of the tournament, the winning bot will be granted 1000 credits to spend on additional parts for upcoming tournaments - under the following conditions:
The bot's physical design may not be subtracted from and/or re-designed to incorporate the new cost limit. You may only stick new parts on the already existing bot design.
You may still change and modify the AI, moves, and paint.
You may only stick on additional components, controllers, energy, sensors, shielding, and weapons. You may not add additional joints or rotators.
You must still adhere to the rules concerning sensor or controller placement.
You may NOT use multiconnect to add the bonus parts.
If you win again, your limit increases to 42k. You may remove and reassign the bonus cost items, but still never redesign the original bot design. And so on...
Any bot over 44k in cost that wins a tournament ascends to Valhalla, is put out to stud, joins the hall of champions, is retired to the Great Hall of Old Fat Lazy Bots, and may not be entered again.
It may be called upon to deal with entry rule-breakers in future tournaments though, or be allowed in as a "house" bot.
Can you believe I actually go through all this? Hard to believe that I can also get laundry done in the same day. :D
Welcome to Roboforge.Servegame.Com ... a site dedicated to robot combat in full 3d glory - the open-sourced 3d Java game: Roboforge all site contents are copyright 2007 Mark De Freitas, other than that which is owned or trademarked by Liquid Edge Games Ltd