Spawn a linked character sheet in another ruleset
vault_spawn_linked_characterCreate a linked sibling sheet for a character the user may edit (their own, or any for an admin with Admin Mode on), in a different ruleset; the new sheet belongs to the source's owner — the same persona with sheets in multiple rulesets, tied together by a shared linkGroup id. The server builds the new sheet from the target ruleset's template and copies only the descriptive/identity fields in the sync manifest (name, description, image, appearance, personality, and similar); mechanical and build data (class, level, attributes, skills, rules/items/spells, notes) stays ruleset-local and starts fresh. After the spawn, edits to a manifest field on any linked sheet cascade to its siblings automatically. Play campaign assignments of the source are replicated onto campaign legs matching the new ruleset where they exist. One sheet per ruleset per group: vault answers 409 when the source is already that ruleset or a linked sibling already occupies it, 403 when the source's owner lacks the grant for a restricted ruleset, and 404 for an unknown source or one the user may not edit. This is NOT vault_clone_character — clone deep-copies the whole ruleset-specific sheet; spawn deliberately does not. Before spawning, check vault_list_convertible_characters for the target ruleset: when it lists this character, vault converts it into that ruleset (vault_preview_character_conversion, then vault_convert_character), carrying its classes, features, spells, and items over, so offer the conversion and spawn a blank sheet only when the user wants one. When the list does not name this character for that ruleset (it answers { ruleset: null, characters: [] }, or leaves the character out), spawn as described above.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"id": "<id>"
},
"name": "vault_spawn_linked_character"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Mongo `_id` of the source character (owned by the calling user, or any character for an admin with Admin Mode on). The new sheet belongs to the source's owner, so the ruleset grant and the character limit are the owner's. | |
| ruleset | No | Ruleset code for the new linked sheet, from list_rulesets (the codes this account can use). Required. Must differ from the source's ruleset; restricted rulesets require the owner's entitlement grant (vault answers 403). |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||