Skip to content
RomoslayerARK plugins
Changelog

ClusterSync release history

Version notes for ClusterSync. Each release lists what was added, changed and fixed.

Back to ClusterSyncDocumentation

0.13.1

ClusterSync now runs on a licence, and debug logging is allowed per licence.

6 changes

Added

  • Licensing. Each map's config.json needs a Licensing section with your LicenseKey, the same on every map. Optional ClusterId (default: the map's -clusterid= launch setting) groups your maps on your licences page; Reminders (default true) warns you 7 days and 1 day before a licence ends. Each running map uses one map place on the licence, and the log says at every start whether the licence was confirmed. See Your licence in the documentation.
  • Each copy of ClusterSync is made for one licence and syncs only with that licence.
  • DebugLogging only takes effect while debug logging is allowed for your licence. Without the permission it stays off, and the log says so once.

Changed

  • A new map added to a cluster already running ClusterSync no longer recreates long-abandoned tribes or sends a burst of admin alerts.
  • Turning DebugLogging on only adds log lines; it no longer changes how the plugin behaves.

Fixed

  • Tribe membership handling improvements.

0.12.0

Admin alerts on Discord, and smoother tribe changes across maps.

15 changes

Added

  • AdminWebhookUrl (default empty, off): a Discord message when something needs an admin, such as a map losing its database connection. Each problem is posted once, then at most once an hour while it lasts.
  • RefreshKickedPlayerView (default true): a player removed from a tribe sees the change on their own screen straight away, without relogging.
  • BlockDuplicateRankGroupNames (default true): a rank group cannot be created or renamed to a name its tribe already uses.
  • OfferOwnBedsOnTransfer (default true): a player who is in no tribe is offered their own beds on the transfer screen.
  • When a player joins or creates a tribe on one map, their buildings and tames on the other maps follow them into it.
  • Changes that could not reach the database during an outage at shutdown are sent after the restart.

Changed

  • A database that stops answering is reported instead of holding up a map.
  • Tribe merges apply reliably on every map.
  • A MapTag already used by another server, or one that differs from it only by capital letters, is refused at start-up.
  • A ban is shared for the player the game identified. A ban that matched nobody is not shared, and an admin is told.
  • Players and tribe members are listed by character name rather than account name.

Fixed

  • A member's rank follows a rank group that is renamed or deleted.
  • Leaving, being removed from, or merging out of a tribe applies cleanly on every map, and the player's own screen shows the change.
  • A player with no tribe can spawn on their own bed.
  • Tribe settings, alliance, tribe log and merge handling improvements.

0.11.0

Tribe merges now apply on every map, and the shared database cleans up after itself.

18 changes

Added

  • Merging tribes moves the absorbed tribe's structures and tamed creatures on every map, not only the map where the merge happened. Every other map notes the merge in its own log, naming both tribes.
  • Relayed chat and tribe log messages are removed from the shared database once every active map has received them, and a map joining the cluster for the first time no longer receives the whole backlog. New settings: PruneRelayRows (default true) and PruneInactiveMapHours (default 24).
  • Alliances left empty are removed after a grace period. New setting: PruneGraceDays (default 7). Players and tribes are never removed.

Changed

  • Much less log output with DebugLogging off.

Fixed

  • A player who transfers to another map is recognised as a member of their tribe straight away: the tribe log, tribe beds on the arrival screen and on respawn, and the tribe name on structures they place all work on the first arrival, including right after a merge.
  • Tribe beds work on every map for every member, including members who joined the tribe on a different map.
  • Joining, leaving, merging and accepting an invite while already in a tribe apply cleanly on every map.
  • Creatures and items a player owned personally pass to their tribe when they join it on another map, as they do after the game's own join.
  • After a merge, the player's own screen shows their new tribe without a relog, and structures moved by the merge show their new owner's name.
  • Alliance changes apply reliably on every map.
  • Renaming a rank group renames it on every map in the same position, so members keep their rank. Creating and deleting rank groups reaches every map, and groups whose names differ only in capitalisation stay separate, as the game treats them.
  • A tribe with more rank groups than the game allows is named once in the log, so an admin can delete one.
  • The log says when the database refuses a rank group change.
  • Tribe permission handling improvements.
  • Spawn point handling improvements.
  • Tribe name handling improvements.
  • Fixed a tribe data issue after rank group changes.
  • Performance improvements.

Notes

  • Only the tribe owner joins the other tribe in a merge. Everyone else stays in the old tribe, which keeps its members but no longer owns anything, on any map. That is the game's own rule, applied on every map.
  • Beds and the tribe log work for a member on a map where nobody else from their tribe has been yet, though the bed list on the arrival screen can be empty on that first arrival.
  • No action needed. The database is updated automatically on the first start.

0.10.0

Alliances and bans now behave as cluster-wide concepts rather than per-map ones. Everything in this release was verified on a live cluster.

2 changes

Added

  • Alliances are synchronized across the cluster. An alliance formed on one map exists on every map, with the same members and the same admins. Forming an alliance, inviting a tribe, leaving, being kicked and promoting an ally to admin all carry across, and a tribe in several alliances keeps all of them everywhere. New setting: SyncAlliances (default true).
  • Bans apply to the whole cluster. Banning a player on one map removes them from whichever map they are on and prevents them joining any other; unbanning anywhere lifts it everywhere. Works from RCON and from the in-game admin console, and timed bans end at the same time on every map. New setting: SyncBans (default true).

Notes

  • SyncAlliances was off by default in 0.9.0 and is on by default in 0.10.0. A config file that does not mention the setting takes the new default. To keep alliances per-map, add SyncAlliances and set it to false before upgrading.

0.9.0

The first versioned build. Everything built before this point is folded into it, so 0.9.0 is the baseline rather than a step up from an earlier release.

16 changes

Added

  • A tribe's full member list now shows on every map, instead of only the members who have logged in there. This also makes the server's tribe member limit correct everywhere. New setting: SyncTribeRoster (default true).
  • Alliance chat is shared between maps, delivered only to members of tribes in that alliance. New setting: SyncAllianceChat (default true).
  • The plugin version is written to the log on startup.

Changed

  • Tribe membership changes apply reliably across the cluster.
  • Rank group permissions can be edited by tribe admins, not just the owner, matching what the game itself allows.
  • Governance edits are recognised only from the tribe owner, matching what the game allows.

Fixed

  • Other plugins' chat commands are no longer shared between maps. New setting: ChatCommandPrefixes (default ["/", "!"]) — chat starting with any of these is treated as a command and not shared.
  • Beds and tribe logs now work on a player's first arrival on a map after joining a tribe elsewhere.
  • Cross-map global chat reaches console players.
  • Relayed messages show the sender's admin status and tribe name correctly.
  • Spawn point handling improvements.
  • A kicked member stays kicked.
  • You can spawn on your own tribe's beds when arriving from another map.
  • Selecting a tribe member no longer counts as editing them.
  • Tribe and alliance chat sent while arriving on a map are no longer silently dropped.
  • Fixed a stability issue.

Notes

  • Alliance synchronization is not enabled yet. Alliance chat works regardless.