The crowns decide. The kingdom carries the consequence.
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.
An illustrative day in Everbloom’s shared-world design.
The King and Queen choose to prepare a festival. The campaign gives the decision a form that can be validated within the world’s rules.
The decision cascades through responsibilities. Players take part in the work; wicker NPCs keep unclaimed roles present.
Completed work becomes a durable consequence in the kingdom. The shared state distinguishes pending tasks from settled changes across servers.
Completed work becomes a durable consequence in the kingdom. The shared state distinguishes pending tasks from settled changes across servers.
Recorded decisions become the basis of the day’s account. The next reign inherits both the state and the history of the kingdom it will govern.
What could these mechanisms make possible for you?
Discuss a living world