Tribe Synchronization
How tribe identity and membership are kept in step.
On this page5 sections
A character belongs to one tribe across the whole cluster. Tribe changes made on any map apply on the others.
What propagates
- Creating a tribe.
- Joining, leaving or being kicked.
- Ownership transfer.
- Member rosters.
- Merging one tribe into another.
Moving between maps
A player keeps their tribe and permissions when moving between maps. The tribe log, tribe beds and the tribe name on structures they place all work from their first arrival, with no need to reconnect.
When a player joins or creates a tribe, the creatures and structures they own personally pass to that tribe on every map, just as they do after the game's own join.
A player removed from a tribe sees the change on their own screen straight away (RefreshKickedPlayerView).
Tribe merges
When a tribe is merged into another, the absorbed tribe's structures and tamed creatures move to the new tribe on every map, not only the map where the merge happened. Every other map also notes the merge in its own log, naming both tribes.
Only the owner moves in a merge
Full member lists
A tribe's whole member list appears on every map, not only on maps those members have logged into.
This also makes the server's tribe member limit correct everywhere.
Beds and spawn points
Tribe beds are available across the cluster, and stop being offered when a player is no longer in the tribe. A player who is in no tribe is offered their own beds on the transfer screen (OfferOwnBedsOnTransfer).
Changes are not instant