1. Team Formation

• Teams must consist of 2-4 participants.
• Participants can register individually, and teams will be formed on the spot (optional).
• Cross-department or mixed-year teams are allowed to encourage diversity in skills.

2. Event Structure

The game will have three rounds:

Round 1: Debugging Blitz

• Participants will be given a set of buggy code snippets in multiple languages.
• The task is to identify and fix as many bugs as possible within the given time.

Round 2: Code Toggle Challenge

• Each team will toggle between coding and solving:
  • One participant writes code for 5 minutes, while the others observe silently.
  • After the toggle timer, another teammate must take over and continue the same code.
  • Communication is restricted until the end of the round.
• Tasks will be problem-solving questions or implementing algorithms.

Round 3: Live Collaboration (Final Round)

• Teams work collaboratively on a complex task requiring dynamic role switching (coding, testing, debugging).
• Judges will observe teamwork, problem-solving approach, and overall efficiency.

3. Participant Guidelines

• Laptops and chargers must be brought by the participants.
• Participants should install the required software (Python, Java, or any other relevant IDEs) before the event.
• Internet access will be restricted unless otherwise mentioned by the organizers.
• Teams must adhere to the time limits during role-switching and avoid external help.

4. Time Limit

• Round 1: 20 minutes
• Round 2: 30 minutes (toggle every 5 minutes)
• Round 3: 45 minutes

5. Scoring

• Round 1: Scored based on the number of bugs fixed (accuracy and efficiency).
• Round 2: Scored on the correctness of the solution, adherence to toggle rules, and code quality.
• Round 3: Scored based on teamwork, creativity in approach, and solution accuracy.

6. Code of Conduct

• Participants must maintain a spirit of fairness and integrity.
• Use of external help, plagiarism, or tampering with another team’s code will lead to immediate disqualification.
• Respect teammates, opponents, and event organizers. Misconduct will not be tolerated.
• Any disputes will be resolved by the organizing committee, and their decision will be final.

7. Winner Declaration

• Evaluation Process:
  The final scores will be a cumulative total from all rounds, based on the following Weightage:
  • Round 1 (Debugging Blitz): 25%
  • Round 2 (Code Toggle Challenge): 35%
  • Round 3 (Live Collaboration): 40%
• The team with the highest total score across all rounds will be declared the winner.