Why I Took the Challenge

I wanted to test my productivity and see how efficiently I could plan, execute, and polish a complete gameplay loop. Working under tight deadlines forces clarity. You cannot waste time on features that do not matter. You focus on core mechanics, clean systems, and smart workflow decisions. This challenge turned out to be an excellent lesson in discipline and rapid prototyping.

Core Mechanics I Implemented

1. Endless Procedural Tile Generation

The environment continuously generates in front of the player while older tiles move behind the camera. This creates the illusion of infinite forward motion without relying on expensive level streaming.

2. Color-Based Scoring

The game features four neon colors: Red, Blue, Green, and Yellow. The scoring system works like this. When the player color matches the tile color, the score increases over time. Collecting a matching obstacle adds ten points. When the player color does not match the tile color, the score decreases. Hitting an obstacle of the wrong color ends the game. This simple system creates an engaging risk and reward dynamic.

3. Random Obstacle Spawning

The obstacle spawner is tied directly to the procedural generation system. This ensures that obstacles appear in logical and playable positions.

My 20-Hour Development Breakdown

First 15 Hours – Core Systems

During this time I focused on building all the fundamental systems. I implemented movement and controls using WASD and Space for jump. I created the tile generation logic and obstacle spawner. I set up color assignment and transitions, the scoring system, and the basic game loop. This phase was fast and focused. The goal was to get a functional prototype rather than a polished game.

Last 5 Hours – Debugging

In the final stage I worked through critical logic bugs. I fixed misaligned obstacle spawns, color mismatches between tiles and obstacles, score calculation inconsistencies, and occasional breaks in the endless-runner system. This final debugging sprint transformed a rough prototype into a stable and playable build.

What I Learned from the Challenge

This project taught me several valuable lessons.

1. Always Plan Your Development Pipeline

Decide what to build first, second, and third. Avoid adding features mid-development just because they sound interesting.

2. Rapid Prototyping Boosts Productivity

Short challenges remove the fear of failure. You try more ideas, focus more sharply, and improve faster.

3. Debugging Needs Dedicated Time

Rushing through bugs while building systems only slows you down later. Separating build time from debug time saved me hours.

Final Thoughts

Creating Endless Neon Runner in 20 hours was an energizing experience. If you are a game developer, beginner or experienced, I highly recommend taking on short time-boxed projects. They sharpen your skills, improve your planning, and boost your confidence in delivering results quickly. I plan to continue refining this prototype and exploring more productivity-focused challenges in game development.