attributeProfile#

Assigns specific values for the attributes defined in attributeDefinitions to a character, class, or item.

Why it matters#

Definitions say "HP, ATK, and DEF exist". Profiles say "the Dark Mage has HP=80, ATK=15, DEF=3". Without profiles you'd have to copy the stat structure into every page, and any change to the definition (renaming atk to attack) would break everything.

Where it usually lives#

• A page of type 👤 Characters (comes with profile + xpBalance + progressionTable).
• Blank pages when you need standalone stats (e.g. a generic NPC, an enemy base).

Singleton — 1 profile per page. For multiple characters, create multiple pages.

Schema#

AttributeProfileValueEntry#

Example#

Profile for a character:

{
  "id": "profile-mage",
  "name": "Dark Mage",
  "definitionsRef": "section-attrs-base",
  "values": [
    { "id": "v1", "attributeKey": "hp",  "value": 80 },
    { "id": "v2", "attributeKey": "atk", "value": 15 },
    { "id": "v3", "attributeKey": "def", "value": 3 }
  ]
}

The definitionsRef points to the section that holds attributeDefinitions. The panel only lets you pick keys that exist there — you can't accidentally add a value for a non-existent attribute.

Cross-ref validation#

If you rename or delete a key in attributeDefinitions, any profiles that used that key:

• remain visible in the panel with an "orphan key" warning
• must be fixed manually (choose a new key or remove the entry)
• do not break rendering — the addon degrades gracefully

Wizard#

The 👤 Characters page type automatically creates:

1. This attributeProfile (empty, with definitionsRef already filled in)
2. An xpBalance (XP curve)
3. A progressionTable (values per level)
4. An attributeModifiers (character-specific effects)

All linked to the same attributeDefinitions you picked in the wizard dialog.

See also#