Information
Right now, to insert a statblock into adventure text, you must create it from scratch or duplicate existing statblock data and format it into a dataCreature object. This proposal suggests either adding a new object type, "statblock", or extending the existing "dataCreature" object to enable it to pull from existing sources somewhat (or exactly?) like _copy functions.
Who would use it?
Homebrewers, converters
How would it work?
{
"type": "statblock",
"name": "goblin",
"source": "MM"
}
Why should this be added?
Most adventures display statblocks of NPCs or monster variants inline in the adventure text. It would be great if we could do the same, without having to manually duplicate existing defined statblocks (currently inside a dataCareature object). Duplicating data like this is error prone, and makes support difficult. Better to have one source of truth updates all references to it when/if it is changed.
orcnog#1874
Indifferent - spap#9812
Indifferent - Reaversfall#5391
Note - MrVauxs#8622
For G: See PF2eTools for examples of such data structure. And make sure Lyra doesn't weep if this gets implemented <:wokejoy:419132568693374976>
Information Right now, to insert a statblock into adventure text, you must create it from scratch or duplicate existing statblock data and format it into a
dataCreature
object. This proposal suggests either adding a new object type, "statblock", or extending the existing "dataCreature" object to enable it to pull from existing sources somewhat (or exactly?) like _copy functions.Who would use it? Homebrewers, converters
How would it work? { "type": "statblock", "name": "goblin", "source": "MM" }
or.....
{ "type": "dataCreature", "dataCreature": { "name": "Unicorn", "source": "MM", "_copy": { "name": "Unicorn", "source": "MM" } }
Why should this be added? Most adventures display statblocks of NPCs or monster variants inline in the adventure text. It would be great if we could do the same, without having to manually duplicate existing defined statblocks (currently inside a
dataCareature
object). Duplicating data like this is error prone, and makes support difficult. Better to have one source of truth updates all references to it when/if it is changed.Votes: +11 / -0 / ±3