Opportunity brief
GLITCHED is a focused, multi-round competitive debugging event designed to test diagnostic speed, systems thinking, and practical fixability under time pressure. Organized by the Game Developers Association (GDA) CRCE.
Guidelines:
- Team Size: Exactly 3 members per team(the team members must be from same year, branch and division). - Eligibility: ONLY FR CRCE STUDENTS ARE ALLOWED. - Inter-college Team Members: NOT Allowed . -
Number of Rounds & Problem Statements:
- Round 1 (Qualification - Online Platform): Pseudo-code debugging involving multiple problem statements, game visuals, and pseudo-code. - Round 2 (Game Debugging): Project/game files containing functional bugs to locate and fix. - Final Round (Finals Challenge): A complex final project containing interconnected systems and cascading bugs.
-
Duration & Structure:
- 2 Days of competitive debugging (Day 1: Qualification Rounds 1 & 2; Day 2: Finals). - Elimination Flow: All registered teams Round 1 (50% qualify) to Round 2 (6–8 teams or 30% qualify) to Final Challenge (1 Winner & 1 Runner-up,1 FE Winner ).
Rules & Regulations:
- Fair Play: Teams must work exclusively on their assigned project/environment. Intentionally damaging, interfering with, or sabotaging another team's project or system will lead to immediate disqualification. - Scope Control: Teams may modify only the specific files or components permitted by the organizers for each round. -
AI & Internet Policy:
- Round 1: Internet allowed, NO AI allowed. Teams must rely purely on problem statements and pseudo-code. No mobile phones or smart gadgets allowed. - Round 2 & Finals: AI is completely allowed strictly for navigating files, understanding codebase layout, and analyzing system architecture—NOT for actual code solving/fixing. Raw AI prompt outputs cannot be directly copy-pasted; manual integration is mandatory due to custom package setups.
- Submissions & Deadlines: All modifications, reports, and final patched project repositories with a clean git commit history must be submitted within the allotted time. Strict deadlines apply. - Final Deliverables: Finalists must submit a patched project repository, clean git commit history, a one-page debugging report, and present a short demo with a live Q&A session with the judges.