Play in multiple Chronicles

Use the same starting character in several games

1. Create and save one independent base character.
2. Submit that base to each ready Chronicle you belong to.
3. Follow each server's application and review process.
4. Play on the separate accepted sheet for each Chronicle. Check the server name before rolling, editing trackers, or spending XP.

Each base/server relationship retains one Chronicle copy. The copies have their own XP, advancements, trackers, rules configuration, and history unless a supported sharing agreement says otherwise.

Transfer a played version

1. Open an approved Chronicle character you own and select Transfer to another Chronicle.
2. Choose a receiving server you belong to and explain the transfer.
3. Submit the played version for admission. This uses the existing character as the transfer source rather than requiring you to re-enter the sheet.
4. Follow the receiving server's review, or its automatic-transfer policy when the required owner agreement and validations permit it.

A transfer does not delete the original server's sheet or promise identical rules in the destination. The receiving Chronicle still controls content and admission.

Owners agree on sharing

1. As the actual Discord server owner, open Chronicle settings → Character creation or Experience & advancement → Sharing & transfers · server owner.
2. Identify the other Chronicle by its Discord server ID. This owner-only relationship form deliberately uses an ID to identify the correct server.
3. Opt in and choose whether to share future XP awards, future advancement and its XP spend, and optionally earlier history.
4. Choose how incoming transfers are handled: staff review or automatic admission when eligible.
5. The other server owner records the matching agreement in their own Chronicle.

Both owners must agree for a category to be shared. Delegated staff and ordinary administrator permissions do not replace the owners' consent. Either owner can opt out at any time; existing history remains recorded.

Merge earlier history deliberately

1. Both owners enable history merging and the relevant award or advancement category.
2. On the receiving character's XP tab, choose Preview history merge.
3. Select an eligible accepted copy of the same base as the source.
4. Inspect the proposed events and confirm the preview while it is current.
5. Review the results. Conflicting events can remain pending rather than silently overwriting the receiving sheet.

The preview expires after 30 minutes and is tied to the player, source, destination, and receiving sheet revision. A history merge is separate from turning on future sharing.

Handle conflicts

Check Sharing needs review on the receiving sheet's XP tab. An advancement that conflicts with current ratings, costs, permissions, or rules is not blindly applied. Ask the receiving staff to inspect the pending event and resolve its cause before retrying or recording a decision.