Skip to the learning chapters
NITROBLASTER In development
A lone road-mender faces an immense living bridge above a rain-dark forest gorge.

IMAGINATION · TECHNOLOGY · GAME CREATION

NITRO-BLASTER

BUILD THE IMPOSSIBLE.

Every world begins with an idea. Discover how we turn imagination into games.

A creator’s journey by Theodore.dev

IN DEVELOPMENT — CONCEPT VISUALS, NOT FINAL GAMEPLAY

DISCOVER THE WORLD WE ARE BUILDINGTHE LISTENING WOOD · CONCEPT STUDY 01

ONE WORLD · THREE WAYS TO EXPLORE

Watch the idea. Play the progress.
Learn how we made it.

01 · THE TEASER

What we want to achieve

A cinematic, illustrated journey through the world we imagine. Concept scenes show the ambition, not finished gameplay.

Watch the video version ↓

55-second animated motion comic · captions and transcript · optional sound

02 · THE GAME

What we have built so far

Take control of the road-mender. Explore the forest, read the Veyr’s warning, then guard, dodge, repel or evade it. Reach the crossing and try an optional local checkpoint.

Play the early game

Playable early production · keyboard or experimental touch · no account

03 · THE LESSONS

How we got here

Follow Theodore.dev’s Creator’s Journey. Explore the real design choices, code, mistakes and tests, then try the creature decision exercise yourself.

Learn how the creature works

Four interactive introductions · beginner explanations and deeper details

Watch the illustrated teaser video

The same six original concept scenes, exported as a 55-second video. Gentle motion and on-screen captions. Deliberately silent; this is concept artwork, not gameplay or the finished cinematic film.

Read the illustrated video transcript
  1. The forgotten road. We were told the wilderness belonged to us. A road-mender reveals amber markings on a rain-dark milestone.
  2. The borrowed kingdom. We built our roads. Raised our walls. An ordinary traveller beneath vast suspended arches and returning mountain stone.
  3. The witness. But every stone remembers what we promised. Amber sap chambers illuminate a vaulted guardian beneath living roots.
  4. The breach. And something has begun to collect. A road-mender surveys a broken causeway beneath hanging counterweights as the immense guardian rises through the mist.
  5. The choice. Stand against the wilds. Or discover why they rose. The road-mender lowers a blade and raises the Witness Frame toward an immense root limb.
  6. The threshold. Nitro Quest. The land remembers. Warm lamps guide the traveller across the restored living bridge toward a distant fortress.

THE CREATOR’S JOURNEY · Theodore.dev

Discover how worlds are made.
Then create your own.

Follow real choices, useful mistakes and tested changes from Nitro Quest. Start with a story, understand the tools, then try something yourself.

4 introductory lessons. No sign-up, scores or streaks. Your exercise choices stay in this page and reset when you reload.

THE LEARNING ACADEMY · The Creature Forge: from shape to behaviour

01

The Hall of Imagination

How a bridge became a creature

Meet the Spanwarden. Learn why a beautiful picture and a working game are different kinds of evidence.

Concept illustration of the Spanwarden, a living bridge made from roots and stone.
Original concept illustration · not gameplay footage

Also connects to The AI Observatory · The Game Workshop.

Explore this chapter’s development story
What we wanted to create
We wanted an ancient bridge that could wake up and choose whether to help a traveller.
Why we chose it
A guardian that carries people gives the story a question: is every frightening creature an enemy?
Tools we used
We used a written lore guide, OpenAI image generation and a website built with React and TypeScript.
What we made
The project has eight original concept illustrations: two hero compositions and six story scenes. A separate captioned motion comic brings the scenes together.
How AI helped
AI helped turn written design instructions into pictures. The original generation record names the tool, but does not record its exact model identifier.
The problem to watch for
A picture can suggest a convincing creature without proving how its legs move or how a player interacts with it.
How we approached it
We kept the design rules in a lore guide and labelled the illustrations as concepts. The public movement demo is shown separately.
How we tested it
The released teaser was checked for image integrity, six-scene controls, keyboard use, reduced motion and a readable version without JavaScript.
What you can try
Draw a creature with a useful job. Label its body parts, then name one movement you would need to test before calling it playable.
What comes next
Next, the game needs separately validated creature movement and encounters. A concept image alone cannot complete that milestone.
Go deeper: the technical idea

An asset record tracks the image's origin and purpose. A rendering test checks whether it loads; an animation review checks whether anatomy stays consistent; a gameplay test checks whether actions and rules work. These checks answer different questions.

YOUR TURN · NO ACCOUNT NEEDED

Interactive lesson controls
What can the Spanwarden illustration above prove?

Choose an answer. You can try again as often as you like.

Read the answer and explanation

The illustration explores a visual design. It does not prove combat, animation or device performance.

02

The GitHub Citadel

A safe path from idea to release

A branch is a workspace for a change. A pull request is an invitation to review it. Neither means the change is ready to publish.

Concept illustration of an unfinished crossing and distant stone arches.
Original concept illustration · not gameplay footage

Also connects to The Testing Grounds · The Cloud Archives.

Explore this chapter’s development story
What we wanted to create
We wanted people to try a small forest exploration demo while the rest of the platform stayed private.
Why we chose it
A small release is easier to understand and test than opening every unfinished feature at once.
Tools we used
We used Git branches, GitHub pull requests, TypeScript, browser tests and Vercel hosting.
What we made
The release added a public entry to the forest alpha. A route rule kept unfinished account, payment and multiplayer pages closed.
How AI helped
Codex helped with implementation and checks. The exact model and reasoning setting for that historical change were not recorded reliably enough to publish here.
The problem to watch for
A successful build did not prove that a public visitor could move through the forest or that private routes stayed closed.
How we approached it
We tested a protected preview, then a production-configured candidate before assigning it to the public website. A previous version was retained for rollback.
How we tested it
The release record includes movement, pause/restart, browser fallback, route isolation and a real rollback rehearsal. Simulated mobile views were not treated as physical-phone tests.
What you can try
Put the release steps in order below. Then explain to a friend why opening a pull request does not automatically publish a website.
What comes next
Next, each useful change can become a reviewed lesson. Accounts and cloud saves need their own acceptance before they open.
Go deeper: the technical idea

Git records commits; a branch points to a line of work; a pull request presents a change for discussion and checks. A deployment is a running build. Testing the exact production-configured artifact avoids assuming a preview and production build behave identically.

YOUR TURN · NO ACCOUNT NEEDED

Interactive lesson controls
Build a safe release path

Select the steps in order. This is one simplified workflow; real teams may repeat reviews and tests.

    Choose the first step.

    What does a pull request do?

    Choose an answer. You can try again as often as you like.

    Read the answer and explanation

    In this example: branch → commit → pull request → review and tests → verify the staged build → publish and check the live site. A pull request invites review; it is not a deployment.

    03

    The Code Forge

    Make pause mean pause

    A tiny true-or-false decision can change how a whole scene behaves. Find the bug in a safe example inspired by our motion comic.

    Concept illustration of an amber-lit marking on a wet stone beside the forest road.
    Original concept illustration · not gameplay footage

    Also connects to The Testing Grounds.

    Explore this chapter’s development story
    What we wanted to create
    We wanted visitors to control the illustrated story: play, pause, move to another scene or read the transcript.
    Why we chose it
    People read and move at different speeds. Giving them control makes the same story easier to enjoy.
    Tools we used
    We used React state, TypeScript, semantic HTML controls and Playwright browser tests.
    What we made
    The motion comic stores whether it is playing and which scene is visible. It also provides captions, a transcript and a still-image mode.
    How AI helped
    AI helped write and inspect code. Running the controls and tests was still necessary; a confident explanation is not a test result.
    The problem to watch for
    Timers, replay and keyboard focus can behave differently after a visitor pauses or closes a player.
    How we approached it
    The player has explicit pause and replay actions, returns focus when closed and honours reduced-motion preferences.
    How we tested it
    The existing browser checks pause the sequence, advance test time, check the scene, replay it and close it with Escape.
    What you can try
    Repair the condition below. The example is deliberately simplified teaching code, not an account of a bug that existed in production.
    What comes next
    Next, apply the same idea to a creature state: waiting, warning, moving or resting. Each transition will need a clear rule and a test.
    Go deeper: the technical idea

    A boolean is either true or false. The ! operator means not. Production code also needs to clean up timers and account for visibility and reduced motion. The exercise runs only fixed, built-in choices; it never executes learner-supplied code.

    YOUR TURN · NO ACCOUNT NEEDED

    Interactive lesson controls

    Teaching example · deliberately contains a bug

    if (paused) {
      advanceScene();
    }
    Which condition repairs the rule?

    Find the condition that should advance a scene only while it is playing.

    Only these built-in choices run in your browser. There is no code upload or remote code execution.

    Read the answer and explanation

    Use if (!paused). The exclamation mark means “not”. If paused is true, the scene must stay still.

    04

    Lesson 004 · The Game Workshop

    How to Bring a Monster to Life

    Meet the Rattleback Veyr. Explore the real prototype’s shape, moving skeleton and decision rules, then test a small behaviour model yourself.

    Rendered study of the actual Rattleback Veyr model, with six limbs, a low skull and mineral back plates.
    Rendered study of the actual 3D prototype · not final gameplay footage

    Also connects to The Hall of Imagination · The Code Forge · The AI Observatory · The Testing Grounds.

    Explore this chapter’s development story
    What we wanted to create
    We wanted an original six-limbed forest creature that a player could notice, understand and safely retreat from. Its broad, low skull, sensory quills and mineral plates came from a written creature brief.
    Why we chose it
    A fair encounter gives clues before danger. The Veyr raises its plates before a lunge. The player can guard, dodge or take a quieter route; defeating every creature is not the only way forward.
    Tools we used
    We used Blender 4.5 LTS for the model and animations, Three.js for the moving 3D scene, TypeScript for the rules, GitHub for review, and unit tests and Playwright for checks.
    What we made
    The recorded asset was built from written shape rules using a Blender script. A hand-drawn Veyr sketch is not recorded. Sketches can help explore a silhouette, but they do not turn into a game automatically: this prototype needs a mesh, a skeleton, animation clips and code.
    How AI helped
    Codex assisted with source code, asset scripts and checks. Its exact model and reasoning settings were not recorded for these assets. AI suggestions still needed inspection, tests and corrections; the model did not decide that the game was ready to release.
    The problem to watch for
    A moving mesh and working rules can disagree. The project also found that a late interaction could use an old on-screen marker prompt after a pause or restart. Passing an art export check would not catch that gameplay bug.
    How we approached it
    The game keeps its animation files separate from its decision rules. Marker interaction now checks whether the game is paused, whether the player can act, and where the player is right now. We added regression checks for the late input.
    How we tested it
    The creature prototype has been checked for six-limb rigs, animation clips, movement, sight, pursuit, warning, damage, defence, retreat, restart and route isolation. Separate save checks reject malformed or future-version data and test a real browser reload. Physical-phone and human learner reviews remain separate; this lesson does not certify the full game.
    What you can try
    In the decision room below, move an imaginary player nearer, put a wall in the way, and advance one decision at a time. Try removing the warning rule. Explain why a fair attack needs a warning before you restore it.
    What comes next
    Next we will refine movement and visual intersections, review the lessons with a human learner and check physical phones where available. The full chapter, cloud saves and game launch still have their own acceptance gates.
    Go deeper: the technical idea

    A mesh is the surface; bones form a rig; vertex weights tell each part of that surface how much to follow each bone. The Veyr’s colour textures are small deterministic images authored by the asset script, with separate roughness and metal values. These are not photographs of a real animal. Animation clips describe motion; the TypeScript state machine selects behaviour. Three.js blends between clips. Lower-detail versions reduce mesh cost. A branch holds changes, a commit records a checkpoint, and a pull request makes the change reviewable. None automatically grants production approval. This page’s decision room is an explicitly simplified teaching model, not the game’s live combat code.

    YOUR TURN · NO ACCOUNT NEEDED

    Interactive lesson controls

    The creature’s decision room

    Change the clues, then advance one decision. This simplified diagram teaches the prototype’s states. It is not gameplay and does not reproduce the game’s distances or timers.

    What can the creature notice?

    Current state: Patrol

    1. Patrol
    2. Investigate
    3. Detect
    4. Pursue
    5. Telegraph
    6. Attack
    7. Recover
    8. Retreat

    Start with a distant player. What should the creature do?

    Try three checks: far away means no attack; a wall blocks detection; a close approach must include a warning. This lab uses fixed choices only. It never runs code supplied by learners.

    Read the answer and explanation

    A visible nearby player can lead from patrol to investigation, detection and pursuit. A warning comes before attack, then recovery. A wall can block detection. This lab compresses the real game’s timing and movement.

    THE LIVING GAME · NITRO QUEST

    What was borrowed
    will be reclaimed.

    Stone, water and living roots once remembered our agreements. A road could pass through a forest. A fortress could borrow a mountain’s strength. Great creatures stood witness.

    Then humanity erased its obligations.
    Now the land is remembering.

    SIX FRAGMENTS FROM A WORLD IN THE MAKING

    Play The Forgotten Crossing: discover three road markers, read the Witness Frame, release the Spanwarden and walk across its back. The original forest encounter remains available for practice. Early-access art and device support are still evolving. Optional checkpoints stay on this browser only.

    Play the forest alpha
    A road-mender reveals amber markings on a rain-dark milestone.01

    The forgotten road

    We were told the wilderness belonged to us.

    An ordinary traveller beneath vast suspended arches and returning mountain stone.02

    The borrowed kingdom

    We built our roads. Raised our walls.

    Amber sap chambers illuminate a vaulted guardian beneath living roots.03

    The witness

    But every stone remembers what we promised.

    A road-mender surveys a broken causeway beneath hanging counterweights as the immense guardian rises through the mist.04

    The breach

    And something has begun to collect.

    The road-mender lowers a blade and raises the Witness Frame toward an immense root limb.05

    The choice

    Stand against the wilds. Or discover why they rose.

    Warm lamps guide the traveller across the restored living bridge toward a distant fortress.06

    The threshold

    Nitro Quest. The land remembers.

    The Spanwarden’s amber chambers glow beneath its vast root-and-mineral bridge body.

    A LIVING WITNESS

    Not everything
    that wakes
    is your enemy.

    For centuries, it carried travellers across the gorge.
    Now the crossing refuses everyone.

    Before you raise your blade,
    ask what it was made to remember.

    THE SPANWARDEN · ORIGINAL CREATURE CONCEPT

    THE DEVELOPMENT JOURNEY

    Follow the forging
    of the realm.

    One carefully built chapter first.
    Every new path must earn its opening.

    THE SKY KEEPS WHAT THE KINGDOM FORGOT

    The Astral Reckoning

    Time holds no dominion here.

    ROADWARDEN INSTRUMENT · CONCEPT STUDY

    A first path is illuminated · explore the traversal alpha
    The full chapter and target-device trials continue.

    Verified state · THE FIRST STIRRING

    The alignment is changing. The world awakens when its seals are restored.
    These celestial cycles are fictional. They do not count down to a launch or guarantee availability. No release date is announced.

    Study the three celestial witnesses

    VAELOR — The Shattered Sun

    Vaelor did not die when it broke. Its separated fires still carry the warmth once lent to stone and root. When a promise is honoured, the fragments answer one another across the dark.

    “What is given leaves a light.”
    The instrument’s earlier forms

    Explore preserved studies and verified earlier forms. Only verified development can change the current mechanism.

    Original fictional cosmology. Celestial names are working names pending IP screening. Concept visuals, not gameplay.

    1. 01
      complete

      THE FIRST INSCRIPTION

      The realm’s first lore and original visual direction are recorded.

    2. 02
      complete

      THE FIRST STIRRING

      The cinematic teaser and Astral Reckoning are live. The game remains in development.

    3. 03
      in validation

      THE PATHS TAKE SHAPE

      The Forgotten Crossing connects forest exploration, a Witness Frame puzzle and a walk across a living guardian. Browser acceptance is recorded; target-device chapter acceptance remains in progress. Optional saves stay on this browser.

    4. 04
      in validation

      THE WILDS AWAKEN

      The Spanwarden has six moving limbs, readable attack warnings and three bindings to release. The original Rattleback encounter remains available. Device review and further art refinement continue.

    5. 05
      planned

      THE PACT IS RESTORED

      The first chapter and reliable cloud saves must be validated together.

    6. 06
      planned

      THE GATES ARE TESTED

      Family safety and target-device trials precede the full chapter release.

    7. 07
      planned

      THE FINAL ALIGNMENT

      The full game release requires separate production approval. No date is announced.

    THE LIVE DEVELOPMENT CHRONICLE

    Real changes.
    Useful lessons.

    These entries describe recorded releases and reviewed engineering studies. New engineering work becomes a public lesson only after verification and editorial review. Repository details and private evidence stay private.

    The Forgotten Crossing · early-access chapter

    A guardian becomes the road

    Theodore.dev’s world now connects three road markers, a readable promise puzzle and an enormous guardian. Release its three bindings, then walk across the same moving body to the far lookout.

    Before

    The forest ended at a closed gorge. The Spanwarden existed in the original story and concept illustrations.

    After

    A six-limbed model raises, warns, attacks and recovers. Its stone deck becomes the real walking route after the player restores the agreement.

    What we learned: A convincing game moment needs art, rules and a path that actually works. Browser play caught roots protruding through the bridge, so we moved them below the deck and added a geometry check.

    Tools, recorded checks and limitations
    Tools
    Three.js, React, TypeScript, GitHub, Vitest and Playwright. Original procedural geometry reuses the existing registered stone and bark textures.
    Historical test evidence
    The recorded source checkpoint passed 99 unit tests and five local chapter browser tests, including a complete journey, touch rune input and denied-storage recovery. A separate desktop profiling sample is not physical-phone certification. Exact-release checks are recorded privately before promotion.
    AI record
    Codex assisted. Exact model identifier and reasoning configuration are unavailable and are not inferred.
    Known limits
    Early-access art is still being refined. New physical-device chapter review and human learner review are pending. Saves and the Way Reopened achievement belong only to this browser; there is no cloud copy or next playable chapter.
    Source record
    Branch, commit and review references are retained in the private release record.
    Try the related lesson

    Traversal alpha · chapter still in development

    A first path you can explore

    A session-only forest route opened with movement, camera controls, markers and an overlook. It uses prototype geometry; it is not the finished chapter.

    Before

    An illustrated world to watch.

    After

    A separate prototype route you can explore.

    What we learned: A small verified release can be useful while the larger game is unfinished.

    Tools, recorded checks and limitations
    Tools
    Three.js, TypeScript, GitHub, Vercel and Playwright
    Historical test evidence
    The historical release record reports 58 unit tests, 14 cinematic checks and 8 alpha checks passing, with focused Firefox and WebKit checks and a rollback rehearsal.
    AI record
    Exact model and reasoning setting not recorded for this historical release.
    Known limits
    Physical Android/iOS testing and sustained performance remain unverified. No accounts, combat, cloud saves or multiplayer are claimed for this released baseline.
    Source record
    Branch, commit and review references are retained in the private release record.
    Try the related lesson

    The First Stirring

    The illustrated world opens

    Original artwork, a six-scene motion comic and the Astral Reckoning introduced the world without promising a release date.

    Before

    Separate concept illustrations.

    After

    A captioned sequence with visitor-controlled playback.

    What we learned: Artwork needs context and accessible controls to become a useful web experience.

    Tools, recorded checks and limitations
    Tools
    OpenAI image generation, React, TypeScript, CSS, SVG and Playwright
    Historical test evidence
    The release evidence records checks of playback controls, captions, keyboard focus, reduced motion, no-JavaScript fallback and protected routes.
    AI record
    OpenAI image-generation tool recorded; exact generation model not recorded.
    Known limits
    Concept illustrations are not gameplay footage. The complete cinematic film remains a separate, unfinished production.
    Source record
    Branch, commit and review references are retained in the private release record.
    Try the related lesson

    Early playable encounter · full chapter still in development

    A creature learns to notice the world

    Play the original Rattleback Veyr encounter, then explore how its moving skeleton and decision rules were built in Lesson 004. The concept teaser shows our ambition; the early game shows our current work; the lessons explain the steps between them.

    Before

    The creature existed as written design rules. A good description alone could not detect or respond to a player.

    After

    The early playable prototype connects a moving rig to detection, warning, attack, recovery and retreat rules. The lesson lets learners test the ideas without running untrusted code.

    What we learned: A monster needs both a believable body and understandable rules. Art checks, logic checks and actual play each reveal different problems.

    Tools, recorded checks and limitations
    Tools
    Blender 4.5 LTS, Three.js, TypeScript, GitHub, Vitest and Playwright. Original creature geometry, rig, texture patterns and animation scripts.
    Historical test evidence
    The recorded protected creature candidate passed 15 browser gameplay checks and 18 website checks. Separate checkpoint work passed five unit cases and three browser cases for saving, reloading and invalid data. These are bounded prototype checks; physical-phone performance and human learner review are not claimed.
    AI record
    Codex assisted. Exact model identity and reasoning configuration were not recorded; they are unknown.
    Known limits
    Early prototype art and controls are still evolving. Physical-phone performance and human learner reviews are unverified. Checkpoints are optional and local to this browser. No cloud saves, multiplayer or finished chapter are claimed.
    Source record
    Branch, commit and review references are retained in the private release record.
    Try the related lesson

    EVERY WORLD BEGINS WITH AN IDEA.

    Build the impossible.
    Start with one small idea.

    Follow the making of Nitro Quest. Learn a tool, test an idea, and find your own way to create.

    Try a learning chapter

    The introductory lessons, teaser and early solo game ask for no account, contact details or notification permission. Exercise choices stay in this page and reset on reload. It uses no advertising or analytics trackers. Hosting providers process routine technical request data. Game content suitability, family controls and commercial terms remain subject to review before later releases. The game includes a non-graphic creature encounter. Optional checkpoints use this browser’s storage and can be forgotten from the game screen; they are not cloud saves. There are no accounts or chat. Touch support is experimental; physical iOS and Android acceptance is pending. All names are working names; no age rating or release date is announced.

    CONCEPT MOTION COMIC · 55 SECONDS

    The land remembers

    The forgotten road · Paused · Still-image mode

    Read the full transcript
    1. The forgotten road. We were told the wilderness belonged to us. A road-mender reveals amber markings on a rain-dark milestone.
    2. The borrowed kingdom. We built our roads. Raised our walls. An ordinary traveller beneath vast suspended arches and returning mountain stone.
    3. The witness. But every stone remembers what we promised. Amber sap chambers illuminate a vaulted guardian beneath living roots.
    4. The breach. And something has begun to collect. A road-mender surveys a broken causeway beneath hanging counterweights as the immense guardian rises through the mist.
    5. The choice. Stand against the wilds. Or discover why they rose. The road-mender lowers a blade and raises the Witness Frame toward an immense root limb.
    6. The threshold. Nitro Quest. The land remembers. Warm lamps guide the traveller across the restored living bridge toward a distant fortress.

    Sound is an optional original synthesised ambient motif, with no speech or licensed recording. The sequence is concept illustration, not captured gameplay.