The carrier never waits
Every side trip trades distance and safety for tomorrow’s fuel. The shared clock makes even peaceful exploration tense.
PROJECT / NORTH STAR
The long way home.
Saved locally
CO-OP EXPEDITION SURVIVAL / 1–4 PLAYERS
Keep the mothership moving.
Risk leaving it behind.
Your megaship is gone. A battered carrier and its tiny fleet must crawl through a hostile, maze-like galaxy—harvesting enough fuel, making uneasy allies, and surviving every swarm between here and home.
◆◆◆
HOME / 18 SECTORS
FLEET-07
Separate, then reunite
Crews scatter into winding pockets, call discoveries to each other, then race back when the mothership needs hands.
Every route leaves a scar
Destroyed pods, allied planets, recruited buddies, and installed relics reshape the fleet for the rest of the journey.
THE 12-MINUTE LOOP
Leave. Gather. Answer the recall.
- 01Read the route1:00
Choose a branch, planet posture, and who stays aboard.
- 02Scatter5:00
Detach pods to mine, trade, rescue, or hunt a relic.
- 03Recall2:00
A swarm, anomaly, or weapon opportunity demands crew aboard.
- 04Survive & refit4:00
Spend the haul, repair losses, and commit to the next route.
OPEN DESIGN QUESTION
What makes a recall exciting?
Try: warning language, time-to-return, partial crew defenses, and rewards for arriving early.
PLAYABLE PROTOTYPE / FLIGHT FEEL
Fly the risk.
A focused handling lab for the player pods: triangular silhouettes, momentum, readable boost, contextual controls, and one-button crew communication. It borrows principles—not assets—from precision arcade flight and clear platformer tutorials.
FUEL 100%CARGO 0TIME 0.0sCONTACTS 0RECALL —
RECALL ACTIVEReturn to the carrier
W or ↑ thrust
QUICK COMMS
Readable at speed
Player color lives in the core and trail; the triangular body always communicates facing.
One prompt at a time
Controls appear when relevant, disappear after use, and return only when the situation changes.
Intent in one tap
Four calls cover the dangerous decisions without requiring voice chat or a complex radial menu.
DESIGN MEMORY / AUGUST 2026
What changed, and why
This archive records the playable decisions we have made together. It preserves the reason behind each change so future tuning does not accidentally reintroduce solved friction.
Flight-feel sandbox
Started with momentum, steering, boost, fuel, gathering, recall, and docking in one focused canvas test.
FOUNDATIONForgiving collection
Expanded the resource contact field so close passes feel intentional instead of arbitrarily missed.
KEPTMore decisive boost
Raised boost impact so spending fuel produces an immediately legible movement advantage.
KEPTOne-button docking
Removed precision alignment. Near the carrier, pressing E simply picks up the pod.
KEPTE to Dock prompt
Added a hotkey callout only when docking is available, with a small animated emphasis.
KEPTSimpler pod, rarer glow
Simplified the fighter silhouette and reserved the stronger glow language for radiant, higher-value resources.
KEPTLocator backdrop
Added a soft local backdrop and cyan chevron when the pod crosses the carrier silhouette.
ACTIVEMoving carrier crawl
The full expedition drill now asks the player to leave, gather, answer recall, and catch a moving home base.
ACTIVETEST COVERAGE / CURRENT PROTOTYPE
One question per drill
Use the smallest drill that can answer the question. The full expedition leg is the integration test; the focused drills remain available when a specific mechanic needs tuning.
| Drill | Primary question | Observe | Current state |
|---|---|---|---|
| Flight feel | Does movement feel expressive and controllable? | Wall contacts, correction time, unnecessary braking | REVISITABLE |
| Resource dash | Does gathering reward a good line without demanding pixel precision? | Near-misses, route choices, boost use | REVISITABLE |
| Recall drill | Is the warning readable and is returning low-friction? | Response time, missed prompt, docking hesitation | REVISITABLE |
| Full expedition leg | Does leaving a moving home base create a compelling risk? | Cargo gained, fuel remaining, recall response, successful pickup | CURRENT |
NEXT DESIGN CONVERSATION
Victory and failure conditions
The matrix deliberately does not lock these yet. Our next discussion can define what ends a leg, what ends a run, which losses are recoverable, and how co-op players share the result.
SHARED PROJECT / VERSIONED SOURCES
Fleeting asset registry
Every sound, song, graphic, and motion keeps a stable gameplay ID, an editable source in its specialist tool, and a runtime handoff. This is the bridge that lets the game and both creative sites improve together.
SOUNDDECK / FLEETING PROJECT
Audio palette
fleeting/pod/boost/standardPod BoostSEEDED
fleeting/recall/warning/urgent-01Recall WarningSEEDED
fleeting/resource/fuel/pickupFuel Shard PickupSEEDED
fleeting/pod/dock/latchDocking LatchSEEDED
fleeting/carrier/engine/cruise-loopCarrier DriftSEEDED
fleeting/carrier/weapon/charge-loopWeapon ChargeSEEDED
fleeting/swarm/assault/phase-01Recall Under FireSEEDED
fleeting/music/journey/long-way-homeThe Long Way HomeSEEDED
MOTIONDECK / FLEETING PROJECT
2D, 3D & motion pipeline
2D RUNTIME ARTPod, carrier, common/radiant shards, locator, dock prompt, route7 MAPPED
3D PRODUCTIONPod, carrier core, docking bay, fuel shard4 PLANNED
MOTION & VFXIdle, boost, radiant pulse, locator, dock pickup, carrier crawl6 MAPPED
fleeting/pod/player/silhouette-2dPlayer Pod SilhouettePROTOTYPE
fleeting/resource/fuel/radiant-2dRadiant Fuel ShardPROTOTYPE
fleeting/ui/pod-locator/overlap-2dPod Overlap LocatorPROTOTYPE
fleeting/carrier/core/slow-driftCarrier Route CrawlPROTOTYPE
SELF-IMPROVING LOOP
1Game brief→2Editable source→3Runtime export→4Playtest evidence→5Reusable template
Fleeting-specific learning becomes an optional SoundDeck or MotionDeck template only after it proves useful. The source recipe remains attached to every runtime asset.
PLAYABLE SPREADSHEET
Expedition balance lab
Tune a single travel leg. The model exposes the central trade: more scavengers bring fuel home, but fewer hands are ready when the swarm arrives.
FUEL 100SCRAP 18HULL 100%STABLE
Drag the pod markers to test risky gathering positions.
GENERATED LEG
Encounter timeline
MODEL READOUT
Stable expedition
Current assumption
One defender contributes 17 power. A scavenger contributes resources, but is unavailable during the recall window.
SYSTEM MAP / V0.1
One pressure loop, many answers
Every feature should feed the journey, the fleet, or the choice to split up. If it touches none of them, it is probably a distraction.
SHARED CLOCKMothership
keeps moving
keeps moving
LEAVEDetach podsfuel risk ↑
EXPLOREMaze pocketsknowledge ↑
RETURNRecall eventdefense ↑
SPENDRefit fleetoptions ↑
ECONOMY
Fuel
Two tanks create the defining tension: shared carrier fuel advances the run; pod fuel determines who can safely roam.
COMBAT
Recall swarms
Threats are announced, then build. Players choose between an early safe return and one last high-value grab.
PROGRESSION
Relics & refits
Relics bend rules for one run. Refit modules permanently specialize the carrier but compete for scarce slots.
DIPLOMACY
Planet posture
Raid for a large immediate haul, trade for precision purchases, or ally for recurring aid and future story beats.
LOSS
Replaceable pods
A destroyed mini-ship returns its player quickly, while the fleet pays scrap and loses its installed pod upgrade.
COMPANIONS
Autonomous buddies
Recruits fill absent-player roles, handle simple duties, and become optional specialists when four humans play.
CONTENT RULE
Planet reward triangle
| Posture | Immediate reward | Long-term value | Primary cost |
|---|---|---|---|
| Raid | Large mixed haul | None; may create hunter events | Hull, reputation, ammunition |
| Trade | Chosen item or repair | Store refresh on later visits | Scrap or specific goods |
| Ally | Small welcome cache | Recurring fuel, buddy, route intel | Mission time and obligation |
EDITABLE SCOPE
Feature board
Keep the first playable honest. Move features as the design proves itself, and capture ideas without letting them quietly become commitments.
LEARN, DON'T JUST PLAY
Playtest log
Each session needs one question, one observable signal, and a decision. Notes without a decision become lore.
SESSIONS
Evidence archive
NEXT TEST / SUGGESTED
Does the crew return by choice?
Run one 12-minute leg with a 45-second recall warning. Do not tell players when to turn around.
- Count who returns before the final 10 seconds.
- Ask what information caused the decision.
- Watch for confusion between pod fuel and carrier fuel.
Pass signal
At least 75% of returns feel deliberate, and one player chooses to risk arriving late for a clear reason.
FROM LAB TO LAUNCH
Build the proof before the galaxy
The first technical goal is a great four-player expedition loop. Content scale, platform packaging, and metagame come after that loop survives playtests.
NOW / 1–2 WEEKS
Paper engine
Lock vocabulary, resource math, route timing, and one swarm recall.
- Balance workbook
- Input + camera spike
- Network architecture decision
PROTOTYPE / 4–6 WEEKS
Ugly fun
One carrier, four pods, one maze sector, one resource, one swarm.
- Host-authoritative co-op
- Drop-in local bots
- Desktop web build
VERTICAL SLICE / 8–12 WEEKS
A remembered journey
Three planet postures, upgrades, pod loss, one recruit, and a run ending.
- Save/profile layer
- Steam input pass
- Mobile performance budget
PRODUCTION
Build the galaxy
Procedural route grammar, content tools, accessibility, matchmaking, and platform services.
- Content pipeline
- Steam + mobile packaging
- Telemetry and balance
COMMITMENT PLAN / DEFINITION OF DONE
Seven gates from idea to stewardship
0Product truthWorkbook + pipeline
1Flight feelPod is fun alone
2Co-op heartbeatSplit + recall
3Vertical sliceMemorable journey
4Content factoryGodot + tools
5Platform betaSteam + mobile
6StewardshipLaunch + learn
STANDING PROMPT
Build the smallest playable proof of Fleeting’s central promise. Work in vertical slices, measure every test, and expand only when the current loop meets its written acceptance signal.
ENGINE DIRECTION
Godot 4, data-first
Godot gives this 2D co-op game a clean path to Steam and mobile, strong scene tooling, an open runtime, and an approachable scripting layer. Keep rules in deterministic, data-driven modules so this web lab can mirror the production economy.
GAMEPLAYGodot scenes + GDScript/C#
↓RULESPure simulation modules
↓DATAResources / JSON content
CREATIVE PIPELINE
Connect your tools
TECHNICAL RISKS TO PROVE EARLY