For special abilities, advantages, disadvantages, consumables, spells, liturgies, rituals and ceremonies see this page

Contribute to abilities

Ability automation coverage

Contribute to automated animations

Extension DB for DSA5/TDE5 in Foundry VTT

This is the database for spell and liturgy extensions and their active effects for Foundry VTT. As there are roughly 3000 extensions distributed among spells, liturgical chants, rituals and ceremonies a complete coverage or functionality is only possible through joined efforts by the community of TDE/DSA. Feel free to contribute, we'll add the effects in intervals to the official modules.

This functionality requires at least Foundry DSA 4.1.0

Contribution

Everyone is invited to add missing keys to extensions. Please create a pull request. Steps involved:

• open the db file where you want to add extensions
• edit the file
• Create a pull request
• Write an issue for effects which are not coverable at the moment but desired

See chapter allowed keys for currently possible modifications.

Set the key "complete" to true if the effect is automated to 100% (some effects might not be possible, see when to "complete")

A proper entry looks like this:

{
    "Ignifaxius": [
        {
            "name": "Intensiver Strahl",
            "complete": false,
            "changes": [
                {"key": "system.AsPCost.value", "mode": 2, "value": 2}
            ]
        },
        {
            "name": "Windender Strahl",
            "complete": true,
            "changes": [
                {"key": "system.AsPCost.value", "mode": 2, "value": 2},
                {"key": "defenseMalus", "mode": 2, "value": -2}
            ]
        },
        {
            "name": "Zwei Ziele",
            "complete": true,
            "changes": [
                {"key": "system.AsPCost.value", "mode": 1, "value": 2}
            ]
        }
    ],
    "Visibili": [
        {
            "name": "Andere Kosten",
            "complete": true,
            "changes": [
                {"key": "system.maintainCost.value", "mode": 5, "value": "8 AsP pro 30 Minuten"}
            ]
        },
        {
            "name": "Keine Aufrechterhaltung",
            "complete": true,
            "changes": [
                {"key": "system.maintainCost.value", "mode": 5, "value": "0"},
                {"key": "system.variableBaseCost", "mode": 5, "value": "true"}
            ]
        },
        {
            "name": "Unsichtbare Kleidung",
            "complete": true,
            "changes": [
            ]
        }
    ]
}

If you are more experienced you can use the tooling of your choice obviously. You can also add a "comment" key if you need to add information:

{
    "name": "Unsichtbare Kleidung",
    "complete": true,
    "comment": "what a wonderful day",
    "changes": [
    ]
}

Allowed keys

The following keys can be used to modify the spells:

1 The damage roll is a string and has to be preceded with a "+" or "-" for mode 2. 2 This is not reflected in spell data yet

See also existing extensions as example.

Allowed mode values

Area effect shapes

Allowed types

• cube
• line
• sphere
• cone

When to "complete"

Setting the key "completed" to true is a completely arbitrary decission. If the automation is working with all required modifiers, set it to true. If it's missing an aspect don't. See following examples:

{
    "name": "Intensiver Strahl",
    "complete": false,
    "changes": [
        {"key": "system.AsPCost.value", "mode": 2, "value": 2}
    ]
}

The automation is not finished because the extension can not add the status burning automatically.

{
    "name": "Windender Strahl",
    "complete": true,
    "changes": [
        {"key": "system.AsPCost.value", "mode": 2, "value": 2},
        {"key": "defenseMalus", "mode": 2, "value": -2}
    ]
}

The automation adds all required modifiers (AsP & defenseMalus). Complete should be true

{
    "name": "Unsichtbare Kleidung",
    "complete": true,
    "changes": [
    ]
}

The automation is barely possible or the effect is fluff. Complete should be true.

Type meaning

number: value has to be a number

boolean: value has to be "true" or "false" (with quotation marks)

string: value can be any text enclosed in quotation marks

Status