RoboCupJunior OnStage Rules 2025

Each team must have 2 to 5 members. Each team member needs to carry a technical role within the team, such as Electrical, Mechanical, Software etc. Each participant can join only one team. No members can be shared between teams and/or leagues.

All team members must be aged 14 to 19 years old (ages as of 1st of July).

All RoboCupJunior OnStage Teams must also comply with the RoboCupJunior General Rules which can be found at: https://junior.robocup.org/robocupjunior-general-rules/

Teams who, in the opinion of the judges, have knowingly produced duplicate robots, costumes, or performance movements (duplicate music is allowed) of another team will be subject to penalties. This applies to any previous RoboCupJunior Dance or OnStage performance. In case of doubts, the team must be able to provide clear documentation of their preparations and how they have come to their idea.

Teams should inform the judges if robotic components have been featured in previous competitions. To gain marks, teams should be prepared to provide insight on how substantial changes have been made between competitions as evidence of the students’ continuing development of the technologies. Teams should specify how innovations have been done with their technologies and provide documentation to support their claims.

Teams have up to two opportunities to perform before the judges.

The duration of the performance routine must be no less than 1:30 minutes.

Each team has a total of seven minutes on the stage. This time includes stage set-up, introduction, and performance routine, including any re-starts due to factors under the team’s control, and the time for packing up and clearing the stage. The timer only stops when the entire stage is clear with no remnants from the previous performance.

When a team is asked to come onto the stage, a RoboCupJunior official starts the timer.

If the time limit is exceeded due to circumstances outside the team’s control (for example problems with starting the music) there will be no penalty. The judges have the final say on any time penalties.

Teams wait on the side of the stage before being welcomed on stage. A technician designated by RoboCupJunior officials will start the music and the audiovisual / multimedia presentation for the performance routine.

Performances will not be live-streamed for general public viewing. Recordings will be edited and released onto the RoboCupJunior OnStage YouTube channel. Teams have an option to request not to publish the recording of their performance .

Teams are strongly encouraged to use the time while they are setting up on the stage to introduce to the audience the performance and the features of their robots.

Teams must indicate the start of their performance clearly with a “3-2-1" countdown to the judges.

Teams must indicate the end of their performance clearly once it’s over (e.g. everyone coming to the front of the stage / thanking the audience for their attention / …).

Teams can restart their routine if necessary, at the discretion of the judges. There is no limit on the number of restarts allowed within the stage-time. ^[1]

The team can restart without reentering the stage and with a clear countdown (3-2-1) to the judges.

Scores and deductions are reset to 0 after the team has requested a restart. Deductions for every restart will be applied at the end of the performance according to the scoresheet.

The team must leave the stage after their time on stage has expired.

Teams may use music or video to complement their performance. If a team uses copyrighted music, they should follow the Copyright Law of the region where the event is held.

Teams are encouraged to provide a visual or multimedia presentation as part of their performance. This can take the form of a video, animation, slideshow, etc. However, the content should be made by the team themselves.

Interaction between the robots and the visual display is allowed and encouraged.

A projector and screen or LED-screen is provided. The organizers cannot guarantee the height above the stage or the size of the screen.

A HDMI and 3.5 mm AUX cable is available on stage through which a laptop or other device can be connected to the display device. The length of the cable cannot be guaranteed.

If music is used, teams must provide their own audio music source. The preferred transport method is to place the sound or video file on a memory stick as an MP3/MP4 file. The memory stick should be clearly labeled with the team’s name and should hold only the required files. It is essential that the music is given to a sound technician or a RoboCupJunior official before the start of a performance session. Teams are encouraged to bring multiple copies of the audio source file.

The size of the performance stage area is a rectangular area of 5 x 4 meters (m) for robots with the 5 meter side facing the judges.

There is a line marking the edge of the 5 x 4 meter stage. See appendix a.

The floor provided shall be made of a flat (non-glossy) white surface, for example, painted MDF (compressed wood fiber). While floor joints will be made to be as smooth as possible, robots must be prepared for irregularities of up to 5 mm in the floor surface. Whilst every effort will be made to make the stage flat, this may not be possible, and teams should be prepared to cope with this uncertainty.

Teams should come prepared to calibrate their robots based on the lighting conditions at the venue.

Teams using compass sensors should be aware that metal components of the staging may affect the compass sensor readings. Teams should come prepared to calibrate such sensors.

Robots must perform autonomously.

Laptops, notebooks, mobile phones, tablets, Raspberry Pi, and other similar devices can be used as robotic controllers.

Teams should construct their own robot rather than using the instructions that come with a commercial kit. Teams are encouraged to design their robot appearance by themselves. If a team wants to use a famous character as their robot, the team should pay attention to the copyright of the character.

A team may have and use any number of robots. Robots may be of any size. However, using multiple robots does not necessarily result in obtaining higher points. Large robots do not count for more.

Teams are encouraged to design their robots to interact with a communication function. Robots are encouraged to communicate with each other during the performance. Suggested ^[2] communication protocols are infrared (IR), Bluetooth (LE and classic), ZigBee, RFID or other localization platforms.

There must be no communication between off-stage and on-stage devices.

It is the team’s responsibility to make sure that their communication function does not interfere with other teams' robots when practicing or performing.

^[3]

Teams should prepare for disruptions in communication protocols and unavailability of Wifi (as outlined in the general rules) before and during the setup and stage time.

Any localization beacons or markers for a robot’s localization system should be placed within the confines of the stage.

Interactive props can be used to add value to the performance.

The kind of props that are considered "interactive" are:

Robots can sense static props to perform a certain task or trigger an action provided that they are placed on the defined stage performance area.

Static props which do not form an integral part of the performance are discouraged since the focus of the performance should be on robots.

Robots may be started manually by human contact, sensor interaction or with remote control at the beginning of the performance.

During the performance, remote control of a robot is prohibited, including pressing buttons, keyboards, phone applications or similar interactions with touch-like sensors. Touch-like sensors are defined as passive sensors that have a logical single function dependent on human actions.

Humans directly influencing sensors to trigger the progression of the performance will not be rewarded highly.

Intelligent interaction should be used to dynamically alter the robot’s behavior. Robots that interact with their environment and respond accordingly will be highly rewarded. Natural human-robot interaction using sensors responding to human gestures, expressions, sound, or proximity is encouraged.

Interaction between robots is highly encouraged. Robots are allowed to physically touch and can interact through sensors and wired/wireless communication.

All robot interactions must be visible to the judges for the entire performance. This includes the initial manual start of each robot.

Any clarifications regarding this ruling should be directed to the committee before the competition to ensure the interaction is permitted.

Human team members may perform with their robots on the stage during the performance. If so, they should make sure not to hide important key components of their robot counterpart(s) from the judges/audience.

In order to keep the focus on the robots, humans on stage should make sure to follow basic acting guidelines (not blocking the view, not standing with their backs to the audience) and be professional on stage.

Refer to the scoresheet for the list of deductions.

All robot movements or interactions that happen outside the performance area will not be considered for the scoring, but will not lead to deductions.

Teams are reminded that humans triggering the progress of the performance via touch-based sensors will be considered remote-controlled interaction and therefore will be considered an unplanned human interaction.

Teams reusing robots without informing the judges in any way will be subject to deductions.

It is the responsibility of the team to ensure that the music and video/presentation is playing correctly before their first performance by liaising with the RoboCupJunior OnStage officials.

Depending on the configuration of the stage and the sound system at the venue, it is possible that the human starting the robot will not be able to see the RoboCupJunior OnStage official starting the audio source and vice versa. Teams should come prepared for these conditions.

The main performance stage is available for teams to practice on. In fairness to all teams who may wish to practice, a booking sheet is used to reserve the stage for a short practice time. Please be respectful of the allocated time.

Every team who practices on the main stage is responsible for cleaning it after use. The stage must be fully cleaned for the next team willing to use it. The team who uses the main stage just before starting the performance judging should clean up at least 10 minutes before the judging starts.

Performances should not include violent, military, threatening, or criminal elements. This includes inappropriate or offensive words (including music) and/or images.

Participants are asked to carefully consider the wording and messages communicated in any aspect of their performance. What seems acceptable to one group may be offensive to friends from a different country or culture.

A team whose routine may be deemed inappropriate to any particular group will be asked to change their performance before being allowed to continue in the competition. Teams who wish to clarify their performance theme or elements of their performance may contact the OnStage League Committee before the competition. Failure to remove inappropriate content will result in disciplinary action.

^[4]

^[5]

Teams should be aware of the proper handling of ^[6] batteries to ensure safety.

Lithium batteries must be transported or moved in safety bags.

Teams should design their robot in consideration of safety. Relative to the size and capabilities of the robots, teams should consider:

Participants should design their robot(s) to be a size that they can easily carry by themselves. Robots should be of a weight that team members can carry and lift onto the stage with ease.

Robots with flying capabilities, such as drones, must be inside of a safety net or tied to an object that’s weight exceeds the drones maximum lifting capacity. The safety rope or net needs to be made of a material that can not be damaged by the drones rotors and needs to prevent the drone from leaving the boundaries of the stage at any time. No free-flying robots are allowed in the venue. Any team planning to use a flying robot must consult with the OnStage League Committee prior to coming to the competition.

To protect participants and comply with occupational health and safety regulations, routines may not include anything that could be considered a projectile, explosions, smoke, or flame, use of water, or any other hazardous substances (contact the committee through the forum when in doubt).

A team whose routine includes any situation that could be deemed hazardous, including the possibility of damaging the stage, must submit a report outlining the content of their performance to the committee two weeks before the competition. The Committee may also request further explanation and a demonstration of the activity before the stage performance. Teams not conforming to this rule may not be allowed to present their routine.

All teams will have up to 20 minutes of technical interview judging during the competition. Which will take place as an in-person meeting with the judges in a separate room at the venue.

Interviews will be judged by at least two RoboCupJunior officials who have also scored the teams poster beforehand.

The Interview Score Sheet is used in the interview judging. It is strongly suggested for teams to read the Technical Interview Score Sheet before the interview to make effective use of the interview.

Teams should have all physical robotic systems present at the interview with copies of all their work in a format that can be easily viewed. This includes any programs, CAD/CAM designs, PCB designs, or wiring diagrams. Each team member must be prepared to answer questions about the technical aspects of their involvement in the robot design, construction, and programming.

Teams are required to submit the software of all their robots together with their technical documentation before the event.

The files may be changed in between their submission and the competition when necessary.

The code is expected to be documented and include comments that explain the basic purpose of its functions/methods.

Teams need to clarify which third party code and/or libraries were used for their performance and why.

The Technical Interviews take place in English. If teams require a translator, they should inform the RoboCupJunior OnStage officials prior to the event to allow translators to be organized.

Extra time will not be given for teams with a translator.

If the judges consider it necessary, teams may be asked to complete a second technical interview.

Teams are required to submit a recorded demonstration to showcase the capabilities of their robots. The aim of the technical demonstration is to showcase how well the team integrated their robotics creations into a perfect performance. They should demonstrate and describe the capabilities of their robots such as interaction with humans or with each other using mechanisms, sensor systems, and algorithms that have been developed by the team.

The maximum length of the video is 6 ^[7] minutes. If it is longer than 6 ^[8] minutes, it will be cut to that time for judging.

Robots should be presented without their costumes and key features of the technologies used should be visible to the audience.

The team should explain how the capabilities have been developed, the challenges overcome, and the technologies integrated. Teams should also provide examples of solutions to any problems/issues during their project development.

Teams will also be required to outline what they believe are their chosen four features that they wish to be scored on during their OnStage performance (See Overview).

Video editing is allowed and should be used to create a technically engaging and informative demonstration of all robots. Teams may wish to include full English subtitles or transcripts.

All team members are encouraged to be actively involved in the presentation.

The Technical Demonstration is assessed according to the Technical Demonstration Score Sheet.

The demonstration needs to be recorded and the video file must be uploaded by the deadline set by the OnStage League Committee.

Each team is required to submit a Technical Description Poster by the deadline set by the OnStage League Committee, which is before the first performance during the RoboCupJunior competition. The purpose of the poster is to explain the technology used, particularly highlight the four chosen features, as well as to showcase the robots’ software and hardware. Posters should be made in an interesting and engaging format, as they will be viewed not only by the judges but also by other teams and visiting members of the public.

Teams must submit a digital copy of their poster in PDF format (≤ 10 MB).

^[9]

Areas that are useful to be included in the poster are:

Teams will be given public space to display their Technical Poster.

Each team will be asked to complete a bill of materials including all major components and materials prior to the event.

The list has to include the following:

A template will be provided and has to be used for the submission.

The judging criteria and allocation of marks are given in the respective score sheets.

Teams must read the Score Sheets carefully so that their robot performance covers as much judging criteria as possible,

The total score of each team is calculated by combining the scores from the team’s Technical Interview, the Technical Demonstration, and the OnStage Performance.

If more than one performance is scheduled, the highest of all performance scores will be used.

The stage performance will be judged by a panel of at least three officials. At least one of these judges is a RoboCupJunior official who has judged the Technical interview and documentation as well.

The judging panel should consist of representatives from each super region and should be selected from a wide range of regions when possible.

It is expected that all participants, students, and mentors, will respect the RoboCupJunior mission, values, and goals.

It is not whether you win or lose, but how much you learn that counts. Choosing not to take this opportunity to collaborate with students and mentors from all over the world means missing out on a lifelong learning experience. Remember this is a unique moment!

It is expected that the aim of all teams is to participate in a fair and clean competition.

Humans that may cause deliberate interference with robots, robots' performance and/or damage to the stage will be subject to disciplinary action. This will be decided by the OnStage League Committee and RoboCupJunior Officials.

Remember, helping those in need and demonstrating friendship and cooperation is the spirit of RoboCupJunior, as well as helping make the world a better place.

Participants are encouraged to help each other.

All behavior is to be of a subdued nature while at the competition. It is expected that every participant behaves in a respectful manner towards each other.

Participants are not allowed to enter team- areas of other leagues or other teams unless expressly invited to do so by other team members. Participants who misbehave may have disciplinary action taken against them.

A team who is not punctual will be penalized. If the team repeats unpunctual behavior, they risk disciplinary action.

The officials will act within the spirit of the event.

The RoboCupJunior officials shall not have a close relationship with any of the teams in the league they judge.

Each team is required to have a mentor to assist with the communication among the team and facilitate their learning. The mentor receives communications from the committee leading up to and during the competition via the email address used for their registration.

Mentors (defined as teachers, parents, chaperones, translators, or any other adult non-team members) are not allowed in the student work area except to assist in carrying equipment in or out of the area on the arrival and departure days.

If a problem is encountered that is beyond the team’s capabilities and is clearly beyond the reasonable ability level of a student to repair, mentors may request assistance from the OnStage League Committee, including supervised support to conduct repairs.

Mentors are not allowed to set up equipment on stage, as this should be the responsibility of team members. Teams should design all robots and any additional equipment to be carried by team members only.

Disciplinary action will be taken should a mentor be found mending, building and/or programming the robot(s), and/or directing choreography. Judges may question the team’s originality if this occurs and teams may risk deductions or disqualification.

It is understood that RoboCupJunior events with rich technological and curricular developments should be shared with other participants.

Team materials may be published on the RoboCupJunior media platforms during the event.

Sharing information furthers the mission of RoboCupJunior as an educational initiative.

If any rule clarification is needed, please contact the International RoboCupJunior OnStage League Committee, using the Junior Forum (https://junior.forum.robocup.org). Once the inquiry is posted on this forum, OnStage League Committee members will respond as soon as possible.

If necessary, even during a competition, rule clarifications may be made by members of the RoboCupJunior OnStage League Committee.

Teams will be responsible for checking for updated information during the event. Methods of communication during the event will be announced to the registered mentors via email before the competition.

Teams are strongly encouraged to check the RoboCupJunior Forum which conveys information about the competition before the competition.

If special circumstances occur, such as unforeseen problems or capabilities of a robot, these rules may be modified by the RoboCupJunior OnStage League Committee Chair in conjunction with available Committee members, if necessary, even during competition.

If any of the team leaders/mentors are not present at the team meetings to discuss the problems and the resulting rule modifications, they consent to the rule modifications and are not permitted to challenge them at a later time.