Code-Wars 4.0

All that you need to know about Code-Wars 4.0 Code-Wars 4.0 The event consists of three rounds, each designed to test different programming skills, including speed, efficiency, and debugging abilities. *Note - All teams need to be physically present at the venue Event Structure: Round 1: Trivia Triumph Objective: Participants will take part in a quiz hosted on Menti, an interactive quiz platform. The questions will be related to coding, algorithms, logical reasoning, or general computer science knowledge. Judgment Criteria: Speed & Accuracy: The fastest and most correct responses will be rewarded with higher points. Since Menti quizzes are real-time and interactive, the earlier a participant answers correctly, the more points they get. Round 2: Byte-Size Battle Objective: Each team will be given a programming problem to solve. The main challenge is to write a correct solution using the fewest characters of code possible. Additional Details: Teams will be pre-planned and paired against each other based on the language they choose to use. This means teams will face one-on-one competition in each matchup and only the winner goes to the finale. The goal is to write a concise yet functional solution. Judgment Criteria: The team with the fewest characters of correct code wins the matchup. If two teams have the same number of characters, the winner will be determined by: Earlier submission time. Execution time and space efficiency, as calculated by the coding platform. Round 3: Bug Buster  Objective: Participants will be given buggy code (code with errors or logical flaws) and will be required to fix all errors as quickly as possible. The focus is on debugging efficiency, not writing fresh code. Additional Details: Teams will also get a 3-minute window to inject bugs into an opponent’s code. This adds a strategic sabotage element, requiring teams to be smart about introducing new bugs while ensuring they can still debug efficiently. Judgment Criteria: The first team to fully debug their code wins. The second team to finish is the runner-up, and so on. If multiple teams complete debugging around the same time, the winner will be decided based on: Time is taken to fix all errors. Complexity and correctness of debugging. Fair Play & Violation Consequences: Plagiarism, unauthorized collaboration, or external help → Disqualification. Disrupting another team (outside of Round 3 bug injection) → Immediate elimination. Unfair debugging (e.g., deleting code instead of fixing) → Penalty points or disqualification. Rules & Regulations: General Rules: Team Composition: Maximum of 2 members per team; solo participation is allowed. Elimination & Qualification: Round 1: The top 50% of teams (max 20 teams) qualify for Round 2. Round 2: Teams face pre-planned matchups; winners advance, losers are eliminated. Round 3: The team that fully debugs their code first wins, followed by runner-ups. Use of External Resources: No AI tools, internet assistance, or plagiarism. No external help or code copying. Conduct & Sportsmanship: Any form of cheating, plagiarism, or misconduct results in disqualification. Teams must respect judges, organizers, and fellow participants. No interference with other teams’ work (except bug injection in Round 3). Final Notes: Judges’ decisions are final and non-negotiable. Any unexpected disputes will be resolved by event organizers. Teams should maintain integrity, play fair, and enjoy the challenge.