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.
Game Style and Theme-
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.
Challenge Design Expectations-
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.
Fair Play-
Participants may discuss ideas with others, but may not share code, assets, or work.
-
All participants must follow the event’s code of conduct.
Requirements
A pixel‑style game that:
-
Requires glitch exploitation to complete.
-
Takes at least 15 minutes for a first‑time player.
-
Runs entirely in a web browser.
-
Supports both keyboard and touchscreen/iPad controls.
-
Demonstrates intentional, discoverable glitch mechanics.
-
Includes at least one section where progression is impossible without using a glitch.
Participants must submit:
-
A web‑playable version of the game (public link or HTML5/WebGL export).
-
A README explaining:
-
The glitch mechanics
-
How they are triggered
-
Any known limitations
-
-
Optional: a short video demonstrating one glitch.
-
All required materials must be submitted before the deadline.
Prizes
GIF or picture
You will get 5 gifs and or pictures of your choice for free
Devpost Achievements
Submitting to this hackathon could earn you:
Judges
Eugene Bonney
GB3-Productions
Judging Criteria
-
rules
the judge will finish the game unless impossible and or game breaks or doesent start
Questions? Email the hackathon manager
Invite others to compete
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
