Dates Hackathon Timeline

Start Date: To be announced by the organizer.

End Date: To be announced by the organizer.

Submission Deadline: All entries must be submitted before the posted deadline. Late submissions will not be accepted.

Judging Period: Judging will begin immediately after submissions close.

Winner Announcement: Winners will be announced after judging is complete.

  Eligibility

  • Open to all individuals.

  • No teams; this is a solo‑only challenge.

  • Participants must submit original work created during the hackathon period.

  • Participants must comply with all rules, content restrictions, and submission requirements.

  • Organizers reserve the right to disqualify any participant for misconduct or rule violations.

  Project and Submission Requirements Project Requirements

Your project must:

  • Be a pixel‑style game.

  • Require glitch exploitation to complete.

  • Take at least 15 minutes for a first‑time player.

  • Support both keyboard and touchscreen/iPad controls.

  • Run entirely in a web browser (HTML5 or WebGL).

  • Be created by a single participant during the hackathon.

Submission Requirements

You must submit:

  • A web‑playable version of your game (public link or HTML5/WebGL export).

  • A README that explains:

    • The glitch mechanics

    • How they are triggered

    • Any known limitations

  • Optional: a short video demonstrating one glitch.

  • All materials must be submitted before the deadline.

  Prizes

custom image hand drawn by professional For free.

  Judging Criteria and Winner Selection Judging Criteria

Entries will be evaluated based on the following:

1. Glitch Design and Creativity How clever, intentional, and well‑designed are the glitch mechanics? Does the game require glitch exploitation to progress?

2. Gameplay and Level Design Is the game fun, engaging, and well‑structured? Does it introduce glitch concepts clearly and progressively?

3. Pixel Art and Visual Presentation Does the game effectively use pixel‑style graphics? Are glitch effects, animations, and visual cues clear and consistent?

4. Technical Execution Does the game run smoothly in a web browser? Are controls responsive on both keyboard and touchscreen?

5. Overall Experience Is the game polished, coherent, and enjoyable from start to finish? Does it meet the 15‑minute playtime requirement?

Winner Selection

  • Judges will review all eligible submissions after the deadline.

  • Each game will be scored using the criteria above.

  • The participant with the highest overall score will be declared the winner.

  • In the event of a tie, judges may conduct an additional review.

  • All judging decisions are final.