MASSIVE MUSHROOM / FIELD NOTESDEVELOPMENT PREVIEW
THE HUMAN-READABLE ROAD TO 1.0

What we're building.
What it means for you.

The design, the evidence, and the work still ahead—translated from development documents into the adventure they are meant to create.

Read the labels, not a progress bar. “Scoped evidence” means a particular change has acceptance or implementation evidence. It does not mean the entire feature is finished, release-ready, or independently playtested here. This is a curated source snapshot, not a live task monitor.
01 · IntentWhat the player should experience.
02 · EvidenceWhat the sources actually support.
03 · BoundaryWhat that evidence does not prove.
04 · NextWhat remains to be resolved.

8 areas · source snapshot: 23 October 2026 · develop / 4559ae54

01

A Vanguard worth bringing home

Scoped evidence

The playable foundation joins persistent heroes, Everholm preparation and consequential expeditions.

What the evidence says

Named heroes, one adventurer per expedition, personal equipment handoffs and deliberate return are documented implemented foundations.

What still matters

More content, balance and long-term progression still need their own proofs.

Technical source details · 2 references

Private repository links require access. The descriptions above are curated for this website; raw internal discussions are not reproduced.

02

Everyday controls, one coherent language

Scoped evidence

The core interface rollout covers creation, hero records, dialogue, inventory, abilities and maps.

What the evidence says

The UI roadmap records accepted increments through UI-016, with separate scope and verification for each.

What still matters

Compendium, settings and later interface work remain; delivered screens do not mean the entire UI is finished.

Technical source details · 1 reference

Private repository links require access. The descriptions above are curated for this website; raw internal discussions are not reproduced.

03

Quests that carry through to a reward

Scoped evidence

Accept a quest, follow its progress and deliberately claim its reward.

What the evidence says

The scoped UI-029 foundation was accepted and merged in PR47. Its record includes log/tracker behavior, manual hand-in and whole-bundle rewards.

What still matters

Continue the owner-requested review of quest behavior; wider regional content and public release are separate.

Technical source details · 1 reference

Private repository links require access. The descriptions above are curated for this website; raw internal discussions are not reproduced.

04

A fourth way to face the darkness

In progress

The Paladin starter kit adds a distinct sword-and-shield class with light-based abilities.

What the evidence says

PR43 merged the starter kit and ability artwork. Focused native/portable checks and Apple builds are recorded.

What still matters

Class feel, dedicated character art and wider platform/release acceptance remain separate; a full mature skill tree is outside the starter slice.

Technical source details · 2 references

Private repository links require access. The descriptions above are curated for this website; raw internal discussions are not reproduced.

05

One complete regional journey

Planned

The next major experience connects the campaign map with a playable restoration loop.

What the evidence says

The UI-017 owner defines map knowledge, regional consequences and a bounded first-region experience. It does not claim completion.

What still matters

Bring the missing systems together, then verify the whole journey. A selected first-region recipe is not a fixed universal quest chain.

Technical source details · 1 reference

Private repository links require access. The descriptions above are curated for this website; raw internal discussions are not reproduced.

06

A workshop for the world

Scoped evidence

Foundry makes asset preparation and hero loadouts more repeatable.

What the evidence says

PR51 merged hero loadouts and reproducible preparation. The tooling roadmap records catalog, CLI, native workspace, equipment-fit and animation foundations.

What still matters

Polish and review existing bodies and handling before broader production. Tool readiness is not automatic final-art adoption in the game.

Technical source details · 1 reference

Private repository links require access. The descriptions above are curated for this website; raw internal discussions are not reproduced.

07

Shared rules, new platform paths

In progress

Portable presentation is being developed alongside the existing Apple game.

What the evidence says

The port roadmap records shared Swift foundations and bounded Windows dungeon, return and save/reload proofs.

What still matters

Full parity and platform qualification remain. Keep the Apple implementation until a coordinated validated cutover; Linux execution is not yet established.

Technical source details · 1 reference

Private repository links require access. The descriptions above are curated for this website; raw internal discussions are not reproduced.

08

The road to a public 1.0

Planned

Internal progress is not the same as a finished public release.

What the evidence says

Source-qualified internal deliveries and accepted milestones provide a foundation for further development.

What still matters

Finish broader content, balance, art and applicable device/service/release gates. No public release date or storefront availability is announced.

Technical source details · 1 reference

Private repository links require access. The descriptions above are curated for this website; raw internal discussions are not reproduced.

Keep the story honest.

A design document tells us where the game is going. A merged change tells us what code changed. A test tells us something specific held under specific conditions. None of those, alone, is a finished player experience.

This preview keeps those distinctions visible. Daily refresh and publication are not automated yet; updates should be reviewed before becoming public.