GLITCHED GAMES

Your mission is to create a pixel‑style game that can only be completed by intentionally exploiting glitches. Players must break the rules, bend the physics, and manipulate the game’s flaws to reach the end. Creativity and clever design are essential.

• Retro pixel art (8‑bit or 16‑bit).

• Simple, readable visuals with glitch effects, distortion, flicker, and broken animations.

• Controls should remain accessible and intuitive.

• A normal first‑time playthrough must take at least 15 minutes.

• You may design multiple short levels or one continuous world with checkpoints.

Your game must require glitches to beat it. Examples include:

• Wall‑clipping to reach hidden areas.

• Inventory overflow unlocking secret items.

• Timing exploits that allow players to bypass obstacles.

• Visual corruption revealing hidden paths or platforms.

• Physics breaks that allow unexpected movement or jumps.

Glitches should be intentional, discoverable, and fun rather than random crashes.

• Each level or section should introduce a new glitch concept.

• Players must experiment and learn how to exploit the system.

• Provide subtle hints through visuals, dialogue, sound distortion, or environmental clues.

• The game should reward curiosity and breaking the game’s logic.

• Recommended engines: Godot, Unity 2D, Construct 3, or any engine that supports pixel art.

• Suggested resolution: 320×180 px or 640×360 px for an authentic pixel feel.

• Keep the total game size under 50 MB.

Your game must be playable using:

• Keyboard controls (WASD or arrow keys plus action buttons)

• iPad or touchscreen controls (virtual D‑pad and on‑screen buttons)

Glitch mechanics must work on both input types.

• Participants may discuss ideas with others, but may not share code, assets, or work.

• All participants must follow the event’s code of conduct.

• rules
  the judge will finish the game unless impossible and or game breaks or doesent start