Everbloom is a shared fairytale game for players who like to build together, so that one reign’s choices change the kingdom the next players inherit.
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.
A royal choice becomes distinct tasks for people in the kingdom. Completed contributions pass through settlement before changing a place; the Chronicle carries those consequences into the next reign.
Enter a shared geography with persistent player records and roles in the kingdom.
Turn a royal choice into role-specific tasks. Each contribution progresses independently, and settlement commits its completed consequence.
Record settled consequences in the Chronicle and pass the world’s history into the next reign. Keep unfinished contributions distinct from completed changes.
Two crowns. Everyone changes the kingdom.
Discuss EverbloomA royal decision reaches far beyond the throne. Players take roles, carry out the work and leave a visible consequence in a shared fairytale world.
Everbloom connects a daily reign to a continuing kingdom. Royal choices cascade into structured responsibilities across player roles. Wicker NPCs keep unclaimed roles present, with a visible distinction between people and stand-ins.
Imagine a decision to prepare a new festival: the ruling choice becomes tasks, those tasks affect the kingdom, and the Chronicle retains what happened. This illustrative journey follows the game’s decision and consequence model.
The crowns decide, the world’s rules check every change, and the Chronicle remembers. Illustrative, with fictional players.
What the research says
Illustrative situations, connected to the mechanisms that make them possible.
Players
A King chooses a response to a threat while a Queen shapes the kingdom’s cultural life.
New players
An important role is empty when someone joins a growing world.
Players and world creators
A successful reign should remain meaningful after its rulers change.
Generated campaigns enter the world through a validated campaign format.
Structural checks, permitted effects and economy limits constrain a campaign before it can change the world.
Server stamps replace generated identifiers. A model’s text cannot assign itself authority over world identity.
Durable crown and settlement logic keep a kingdom coherent across servers, interrupted closes and repeated delivery.
A completed action belongs in the shared state before it becomes part of the day’s story.
Treasury and world updates distinguish pending work from durable settlement.
The Chronicle derives its account from recorded decisions. Player identities are handled separately from generated prose.
The next reign inherits the kingdom’s state and history. The world’s continuing condition gives later choices their context.
The design centers on a shared kingdom, a King and Queen, distributed player roles and persistent consequences across a reign.
Discuss living-world design, creative collaboration or access to the current experience. We can connect the conversation to the relevant stage of Everbloom’s development.
The technical choices that give Everbloom: Crown of the Day its particular behavior.
A King and Queen shape Everbloom’s shared fairytale kingdom. Decisions cascade through player roles, validated campaigns change the world, and durable state and the Chronicle connect one reign to the next.
Bound the event. Structural checks, permitted effects and economy limits constrain a campaign before it can change the world.
Keep identity with the server. Server stamps replace generated identifiers. A model’s text cannot assign itself authority over world identity.
Share one reign. Durable crown and settlement logic keep a kingdom coherent across servers, interrupted closes and repeated delivery.
An illustrative day in Everbloom’s shared-world design.
Follow the storyWhat should the next reign inherit from yours?
Discuss Everbloom