• Hackathon Radar
Hackathons
  • Browse
  • Judge Opportunities
  • Sponsors
  • Organizers
  • Map
  • Discover
Personal
  • Custom Views
  • Passport
  • Favorites
Explore
  • Stats
  • State of Hackathons
  • Changelog
  • Settings

GLITCHED GAMES

devpostHosted on Devpost

Fetched 18 days ago

Thursday, April 16, 2026

to Tuesday, June 30, 2026

•

2 months long

Data ScienceWeb DevelopmentArtificial Intelligence
Student only
This hackathons is only open to students. Double check the event page for more information as this may mean only those from a particular university/country are eligible.

Event Type

online

150

Participants

13

Est. Projects

About the Challenge — HACKED 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. 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. Playtime Requirement A normal first‑time playthrough must take at least 15 minutes. You may design multiple short levels or one continuous world with checkpoints. Required Glitch Mechanics 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. Technical Requirements 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. Cross‑Platform Play (Required) 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.

Judge Accessibility

Organizer email available25/25
Student-run event15/15
Actively looking for judges25/25
Small event (120 participants)10/10
No corporate sponsors10/10
New or emerging organizer10/10
Public registration available5/5
Online format (judge from anywhere)10/10

Top signals

Organizer email available
Student-run event
Actively looking for judges

Organizers

Alex Johnson

alex@example.org

Jamie Rivera

jamie@example.org

Sam Chen

sam@example.org

Estimated Audience

Mostly Students
ExperienceStudent
OccupationStudents
Beginner Friendly
Women in Tech

Technical Focus

AI95%
Web80%
Mobile25%

Industries

Healthcare
Education
Climate

Technologies

Python
React
OpenAI

Why this estimate

  • • Hosted by a university
  • • Open to students
  • • MLH member event

Estimate inferred from event metadata, not actual attendee data.

Quality Score

Quality Score

72/100
High confidence
Organiser16/20
Event Maturity14/20
Sponsors18/25
Participants12/20
Operations12/15

Why this score

Strong organiser track record
Returning event
Well-sponsored

Missing data

Prize details
Code of conduct