Living worlds is Naevum's design work for studios building shared game worlds, so that one player's choice changes what others find and generated events stay inside the world's rules.
Retain crowns, current world conditions and the next reign context.
Durably committed world change.
Retained history available to later choices.
Retain crowns, current world conditions and the next reign context.
Reign identity and crown/role context.
Durable world/player assets differ from ephemeral coordination.
Durable world and player state remain separate from temporary coordination.
Constrain a royal choice into structured role-specific tasks.
The Lantern Feast royal choice.
Current kingdom rules and reign identity.
Constrain a royal choice into structured role-specific tasks.
Permitted effects, economy limits and server-owned identity.
Distinct player roles and visible wicker stand-ins.
The structured campaign follows declared world limits and identity rules.
Keep garden, bridge and market tasks independently in progress or complete.
Separate garden, bridge and market responsibilities.
Independently supplied progress/completion for each identified task.
Keep garden, bridge and market tasks independently in progress or complete.
Garden remains unchanged until its completion.
Bridge completion is independent of the other tasks.
Market work and actual contribution event.
A proposed task does not complete a garden, bridge or market contribution.
Commit actual completed consequences under the authoritative world rules.
Only the actual completed branch with its task identity.
Server-owned settlement and economy rules.
Commit actual completed consequences under the authoritative world rules.
Proposed work and independent completion identity agree.
Pending, settled, refused and unavailable state remain distinct.
Only the matching independently completed contribution can settle its consequence.
Write from retained decisions/consequences and pass world history onward.
Settled events, not generated descriptions of hoped-for events.
Write from retained decisions/consequences and pass world history onward.
Recorded events precede prose; player identity remains separate.
The next reign inherits actual settled state.
Recorded events precede the story, and only settled state passes into the next reign.
Durably committed world change.
Retained history available to later choices.
Retain crowns, current world conditions and the next reign context.
Reign identity and crown/role context.
Durable world/player assets differ from ephemeral coordination.
Durable world and player state remain separate from temporary coordination.
The Lantern Feast royal choice.
Current kingdom rules and reign identity.
Constrain a royal choice into structured role-specific tasks.
Permitted effects, economy limits and server-owned identity.
Distinct player roles and visible wicker stand-ins.
The structured campaign follows declared world limits and identity rules.
Separate garden, bridge and market responsibilities.
Independently supplied progress/completion for each identified task.
Keep garden, bridge and market tasks independently in progress or complete.
Garden remains unchanged until its completion.
Bridge completion is independent of the other tasks.
Market work and actual contribution event.
A proposed task does not complete a garden, bridge or market contribution.
Only the actual completed branch with its task identity.
Server-owned settlement and economy rules.
Commit actual completed consequences under the authoritative world rules.
Proposed work and independent completion identity agree.
Pending, settled, refused and unavailable state remain distinct.
Only the matching independently completed contribution can settle its consequence.
Settled events, not generated descriptions of hoped-for events.
Write from retained decisions/consequences and pass world history onward.
Recorded events precede prose; player identity remains separate.
The next reign inherits actual settled state.
Recorded events precede the story, and only settled state passes into the next reign.
An illustrative game design: completed contributions change the world and enter its history.
Additional mechanisms are described in the technical reference.
What the research says
Generated characters now sound like real people, and public bodies fund shared simulated worlds. In both, the hard part is one agreed state: Everbloom settles each decision once on the server and retells its history from what was recorded.
A shared world becomes interesting when choices reach other people and leave consequences they can recognize.
Design roles, responsibilities and persistent state together. Generated events can add variation inside a world grammar; players need to understand what changed and how their participation mattered.
Generation, identity and durable state have distinct jobs.
Check the campaign structure, permitted effects and economy constraints.
Keep server-owned identity and durable settlement coherent across retries.
A shared history should derive from the recorded decisions of that world.
A creative director decides which generated events may change the shared map; the server settles each one once. Illustrative, with a synthetic kingdom.
Systems behind it
A shared, consequential game world
Everbloom is the working proof: one gated writer settles each royal decision once, and the Chronicle retells it.
Evidence-led research & invention
The Vault supplies the settlement and record mechanisms with their assumptions, so a new world starts from tested parts.
Observe whether participants understand their roles and consequences, whether state remains coherent and whether the intended interaction is compelling. Public retention claims need real player evidence.
Validate the event. Check the campaign structure, permitted effects and economy constraints.
Commit the consequence. Keep server-owned identity and durable settlement coherent across retries.
Retell from evidence. A shared history should derive from the recorded decisions of that world.
An illustrative day in Everbloom’s shared-world design.
Follow the storyWhich choice in your world should every player see the consequence of?
Discuss a living-world collaboration