DAY OWLS / DEVELOPMENT JOURNAL
From browser
to the grid.
The evolution of Rogue Racing: a card-driven racing idea grows into a three-mode 3D game and a world-building toolkit.
October 5, 2026 · Private development build 0.7.0-dev25 · Illustrated retrospective
01
The browser beginnings
The project began as Apex Rogue, a race-management prototype with strategy, car development and rewards. It then pivoted toward the central idea of Rogue Racing: managing a hand of cards to control a race. The early section-based rules were experiments, not the current ruleset.
Reconstructed scene from preserved early browser code; original HTML controls are not included.02
Cards moved into the cockpit
The web version grew from a circuit overview into a forward-facing road scene. A steering-wheel interface brought cards, battery, grip and speed together. Later revisions moved toward distance-based movement and more legible corner decisions.
Historical browser scene reconstructed from preserved code, without the layered HTML dashboard.03
A circuit worth studying
Illustrated briefings made the circuit a place to explore before racing. Clickable sections connected the artwork to rules. That combination of attractive map art and useful corner information became a lasting design goal.
Historical illustrated browser briefing reconstructed from the embedded artwork and section overlay.04
The move into 3D
The native Godot prototypes brought the race into a physical space. Tabletop racing, outdoor karts and a cockpit presentation became three distinct ways to experience the game. Licensed Synty assets supplied cars, buildings and props.
Archived native tabletop prototype capture.05
Three modes, one racing identity
R3 emphasizes deliberate tabletop turns, R2 uses kart racing with a close follow camera, and R1 runs continuously. Subsequent playtests refined camera follow, look-around controls, minimaps and the transition between available views.
Archived native cockpit prototype; the current interface has evolved further.06
Drivers and progression
Persistent profiles, discoveries, championships and career progression gave races continuity. Driver creation gained outfit choices and posed portraits. Tester access became explicit, while all new starting decks stayed restricted to base cards.
Development capture of driver selection; menu layouts continued to evolve.07
Building the world ourselves
The asset browser became a Track Decorator, with visual placement, transform controls, drafts and submitted layouts. The current build exposes regional props for editing while keeping track geometry and permanent pit buildings fixed.
Current decorator development capture. Existing user drafts are preserved.08
Thirty places, not one repeated backdrop
All thirty track illustrations now have regional art direction, with urban, rural and coastal settings and seasonal variation. The immediate circuit and infield stay flat to support scenery editing. Clickable corner markers and a stable information panel reconnect the native game to the web briefing idea.
Current integrated illustrated track-select screen. Artwork is a visual target, not an exact screenshot of the playable scenery.09
Scenery enters the race
Available 3D assets now give venues different buildings, vegetation and ground palettes. Coastal venues gain an editable animated water surface. The playable scenes approximate the illustrations; detailed distant cities and mountains remain beyond this pass.
Coastal race development capture. Flat terrain and first-pass water remain intentional limitations.10
A more physical tabletop
The R3 room now displays two randomly selected framed track illustrations with Rogue Racing branding. The mode display tables also use actual track geometry and regional props, connecting menus with the race itself.
Current framed track-art posters in the tabletop room.11
Mistakes that read clearly
Fuel exhaustion now steers a car onto the shoulder. Spin cameras follow the approach and then hold at the failed check. Closer tyre barriers leave a pull-off lane, and contact during a spin releases physical tyres that tumble away from traffic. Existing penalties stay authoritative.
Contact-driven tyre reaction test capture. Debris is temporary and constrained clear of racing and pit traffic.12
Pit stops get a crew
The pit road is now a continuous rounded surface. A procedural two-person crew uses the existing character, tyre and fuel-can assets to stage service actions. R1 briefly pulls the camera back to reveal the work before returning to the cockpit. Timing and resource rewards are unchanged.
New pit-service presentation in dev25. A first-pass crew animation, not a full wheel-removal simulation.