Practical guide
Community worlds and independent branches
How Community worlds are published, versioned, discussed, and launched as independent campaign branches.
Short answer
A published world is a stable public root with an immutable launch version. A branch creates a separate private campaign with provenance without copying another player's turns or mutable state.
What to do
- An author creates a draft or imports a compatible save.
- After successful compilation, the author selects one immutable version and publishes it.
- A player launches an independent branch; it becomes public only through a separate explicit share action.
Practical scenario
Two players start version 3 of the same world. Their heroes and later events diverge, but both campaigns retain the same verifiable origin version.
Limitations
- Publication does not expose private turns, credentials, or hidden source-campaign facts.
- Comments, reactions, and popularity do not change game canon or buy ranking.
Common question
Will my branch change when the author updates the world?
No. It retains the exact origin version; a newer publication applies only to new branches.