Progress and projection

Dates attached to outcomes—not promises.

Three foundation milestones are met. The following dates are estimates for a representative campaign slice, not for completing the entire galaxy.

Planning basis. Briana has stated 40–50 hours per week for development direction and playtesting. This planning baseline assumes sustained availability, AI-assisted implementation during authorized sessions, and no hired team or round-the-clock autonomous operation. That availability is not equivalent to a staffed engineering/art team. Velocity, asset workload and external review lead times remain unmeasured; dates are low-confidence estimates, not commitments.

Re-estimation checkpoints: completion of M04 and M05. If they slip or reveal substantial rework, revise every dependent date before presenting a campaign date as firm. No automated monitoring or standing background work is implied.

Met goals

Completed milestones · evidence dated 6 September 2026
MilestoneStatus / dateCompletion conditionDepends on
M01
Direction and first-playable scope
Met
6 September 2026
Windows/Unity direction, multiplayer-first approach and a bounded town-and-terrain starting slice recorded.

Decision record

Briana’s design decisions

O01

M02
Networked movement foundation
Met
6 September 2026
Separate server/two-client and host/client checks observe moving players; Windows build runs.

Local executable tests

M01

O02

M03
Shared sandbox and saved world edits
Met
6 September 2026
Mine, place and retain the expected inventory and terrain through server restart; 19 state checks pass.

State + live network tests

M02

O03

Open the supporting test records and limitations.

Provisional delivery windows

Proposed schedule · low confidence until velocity is measured
MilestoneStatus / dateCompletion conditionDepends on
M04
Hands-on sandbox acceptance
Estimated
7–13 September 2026
Briana tests two windows; controls, overflow pickup and recovery cases are reviewed; blocking defects corrected.

Acceptance record needed

M03

O04

M05
Forest-town visual slice
Estimated
14 September–11 October 2026
Hill town and visible spaceport landmark, coherent original pixel textures, lighting and readable interface; antenna array subject to approval.

Playable scene + asset register needed

M04

O05

M06
Sound and interaction feedback
Estimated
12–25 October 2026
Original or appropriately licensed ambience, footsteps, mining/building sounds, volume controls and visual alternatives for essential cues.

Audio build + rights record needed

M05

O06

M07
Small crafting and survival loop
Estimated
26 October–22 November 2026
Proposed 15–30 minute gather → craft → construct → sustain loop works in multiplayer; exact recipes and survival needs require scope approval first.

Repeatable scenario needed

M06; finite feature scope

O07

M08
Multiplayer and persistence hardening
Estimated
23 November 2026–3 January 2027
Agreed small remote test cohort, reconnect/save recovery and measured server load; authentication and hosting feasibility assessed before external testing.

Security/performance/test records needed

M07; tester and hosting arrangements

O08

M09
Campaign demonstration candidate
Estimated
4–31 January 2027
A stable, textured and sounded build supports uninterrupted gameplay capture; footage identifies actual gameplay versus concepts.

Tagged build + footage + known issues needed

M08

O09

M10
Kickstarter readiness decision
Proposed gate
9 February 2027
Readiness checklist reviewed by Briana: demonstrated slice, rights, costed delivery plan, campaign scope, external review and publication approval.

No launch authorization yet

M09; budget and campaign materials

O10

M11
Kickstarter launch
Conditional target
9 March 2027
Launch only after the readiness gate passes, current platform requirements are checked and Briana explicitly authorizes publication.

Not launched; not promised

M10; launch preparation and approval

O10

Beyond the campaign

Island/water/vehicle Test 2, scalable universe architecture, NPC economies and the strategic layer need separate feasibility work. Their delivery dates are unestimated. Assigning precise dates now would imply a level of staffing, technical certainty and funding that does not exist.

The planned month between the readiness decision and launch allows campaign preparation and review. It is not a guarantee of platform review times, audience growth or funding success. A failed readiness gate moves the launch; it does not waive the gate.