Systems
Account Data Transfer
When a player changes account, an administrator can move all of their progress onto the new account with one command. The old account ends up with no progress.
Command
Requires the controlserver privilege. The command comes from Arcanum Lib (1.0.0-rc.13 or newer).
| Command | Description |
|---|---|
/arcanum transfer <from> <to> | Shows what will happen. Nothing is changed |
/arcanum transfer <from> <to> confirm | Runs the transfer. Cannot be undone |
/arcanum transfer status | Transfers still waiting for an account to join |
Both accounts must have joined the server at least once, so log in once with the new account first.
What moves
Quests, achievements, titles, reputation, runes, playtime, records, pity counters, pets, karma, chat announcement preferences and the website stats. Progress stored on the player entity moves when each account is next online; mod data and the website database move at once.
How values are merged
The target keeps what it already has and receives the rest:
- numbers add up, except times, levels and records, which take the larger value (and "first ..." values, which take the earliest)
- booleans are OR-ed
- text keeps the target's value
- lists are united
- objects merge field by field
- dialogue variable flags are never added: the target keeps its own, missing ones are copied
- pending rewards are copied only when the target has none
For Mod and Pack Authors
Any new per-player store must register with the transfer system, or it stays on the old account. In the framework this is done in QuestPlayerTransferSetup (src/Systems/PlayerTransfer/) and, for the shared engine, ArcanumLib (PlayerDataTransfer):
| Registration | Use |
|---|---|
RegisterEntityAttributePrefix(prefix) | Player attributes that are progress. This is an allow-list: most vsquest:/alegacyvsquest: keys on a player are transient combat state and must not follow the account |
RegisterEntityAttributePrefix(prefix, fillOnly: true) | Copied only when the target has none |
Register("id", ctx => ...) | Custom participant for world-level stores |
RegisterCustomDataPrefix / RegisterCustomDataMerger | Per-player custom data with a custom merge |
Keys written by quest actions (addplayerint, addplayerattribute) are tracked per quest and move automatically. Values where lower is better or that must not add (best times, unlock times, lockouts) need an explicit merge function.