/ THE WORKSHOPPUBLIC DEVELOPMENT / RYAN POND
A momentum-driven bicycle courier game where mastering the city is as important as mastering the bike.
From a proven ride to a complete game.
This is the actual development plan I am working from, not a fixed marketing schedule. Milestones, priorities and scope may change as the game is built and tested. When they do, the roadmap will be updated and the devlogs will document why.
CURRENTLY BUILDING
Defining the production workflow for creating environments and reusable assets in Blender and Krita and integrating them efficiently into Godot.
See the current phase milestonesDOOM DELIVERY is being developed independently on a minimum 12-hour weekly schedule: approximately two hours per day, six days per week. Some weeks may include additional development time, but 12 hours is the baseline commitment the roadmap is planned around.
The story so far, newest first. Weekly production logs will join the prototype history as the work progresses.
PROTOTYPE HISTORY /
What player feedback taught me, why the bike controller is worth building on, and the next steps beyond the jam prototype.
Prototype · Production Foundation
Documented milestones
PROTOTYPE HISTORY /
Finding the game in a bicycle controller, fixing collisions, and finishing a first 3D game.
Documented milestones
Read devlogOpen a phase to inspect its purpose, milestones and related development logs.
Prove that controlling the bicycle and completing deliveries is enjoyable enough to justify developing DOOM DELIVERY into a full game.
DOOM DELIVERY began as a game-jam prototype built around an unusual bicycle controller: alternating Q/E inputs generate pedaling and momentum, while terrain, slopes, steering and collisions shape the ride. Player testing showed that the movement itself was enjoyable enough to take the project beyond the jam and develop it into a polished standalone game.
Core gameplay concept validated. Players responded positively to controlling the bicycle.
Turn the successful prototype into a stable production foundation capable of supporting a polished complete game.
Defining the production workflow for creating environments and reusable assets in Blender and Krita and integrating them efficiently into Godot.
Build a small section of DOOM DELIVERY at approximately final-release quality to prove the production pipeline, visual identity, gameplay systems and performance targets.
The goal is a polished 5–10 minute experience, not a large amount of content. This slice should prove what the finished game looks and feels like.
Build the first complete interconnected DOOM DELIVERY city using the production pipeline established during the vertical slice.
Route density is more important than raw geographic size. The city should feel like a complete ecosystem, with recognizable areas and better routes to discover.
Expand the proven movement and world systems into the complete game structure.
Planned systems remain subject to iteration and testing; they are not guaranteed final content.
Expand the game using the mature production pipeline and reusable asset library.
Current launch target: up to three distinct maps, subject to production testing and scope evaluation after Map 01.
Bring the complete game to release quality across supported PC hardware.
Optimization is a core development priority, not an afterthought.
Prepare, test and publish the complete release.
No launch date is set.
Stylized mid-poly 3D, inspired most strongly by the readability and angular modeling of Gunfire Reborn. Visible geometry, intentional angles, simplified forms, moderate detail and strong silhouettes should make a believable city readable at speed.
Stylized color and strong lighting, without photorealism, aggressively low-poly shapes or a bubblegum mobile-game look.
Maps will be deliberately designed, using reusable houses, building sections, roads, streetlights, benches, vegetation, fences, signs, vehicles and common props where they make sense. Hero landmarks and important locations should feel more individual.
The goal is a city worth learning, not a world that looks procedurally generated or visibly tiled.
Windows is the primary 1.0 target. Linux and macOS are also intended. Controller support is planned alongside keyboard controls.
Steam Deck and consoles are possible future targets, not 1.0 commitments.
The game must remain testable on a Framework 13 laptop using integrated graphics. That constraint shapes the asset pipeline and optimization work throughout development.
Specific minimum requirements will follow measured testing.
The original jam build is available in the browser and for Windows while work on 1.0 continues.
KEEP IN TOUCH
New games, useful experiments, and the occasional lesson learned the hard way.