Wiki Release: 2026.09.5 · UltimateClans: 9.1.4 · Documentation branch: 9 · ClanDataExchange
ClanDataExchange practical usage guide#
ClanDataExchange adds administrative migration/data exchange from supported clan ecosystems such as ClansLite/SimpleClans-style sources into the UltimateClans data model. This guide focuses on the actual administrator and player workflow: what to set up first, how to test it in-game, and what to check before enabling it for everyone.
How the feature works#
In normal use, the feature follows this flow: Take a full backup of both source plugin data and UltimateClans storage. Run the exchange only on a staging copy first. Select the supported source/migration task and review console output for skipped/converted records.
Recommended in-game workflow#
- Take a full backup of both source plugin data and UltimateClans storage.
- Run the exchange only on a staging copy first.
- Select the supported source/migration task and review console output for skipped/converted records.
- Validate clan count, leaders, members and critical metadata before allowing players online.
Administrator setup checklist#
- Never treat migration as a reversible live command; backup is the rollback.
- Do not run repeated imports into a populated target unless the migration path explicitly supports idempotency.
- Keep source plugin files unchanged until validation is complete.
Changing settings safely#
- Back up the component configuration and persistent data before changing a live server.
- Change one feature area at a time.
- Reload only if the component documents reload as safe; otherwise restart the server.
- Test with a non-OP account that has exactly the intended clan role/permission.
- Watch the console from the first relevant warning/error, not only the final stack trace.
- On multiserver networks, repeat the check on every node and confirm shared storage/sync settings match.