Open Stackclash opened 6 months ago
Item properties are absolutely already taken into account provided they are in the right format in _meta. The Herbalism Handbook works properly, IIRC.
The meta for that handbook does not include a description. This shows in rules/item-properties.md:
### Herb
_Source: Hamund's Herbalism Handbook p. 5_
And items are linked to it:
# Aboleth Stalk
*Herb, rare, Herb*
- **Properties**: [Herb](rules/item-properties.md#Herb)
- **Cost**: 500 gp
What is missing?
@ebullient the properties for "Location" and "Requires Preparation".
"customProperties": {
"lcn": "Mountain",
"prep": "Yes"
}
The lcn
and prep
keys.
ok. A different kind of custom properties. ;)
Herb is, in and of itself, a custom Item property (at a macro level), so I didn't see the detail that you meant.
Always item template usage?
I'm imagining something along the lines of the following in the item template:
Location: {resource.custom.lcn}
Requires Preparation: {resource.custom.prep}
Always item template usage?
Not necessarily, if you wanted a stress test try https://github.com/TheGiddyLimit/homebrew/blob/master/magicvariant/aeyana%3B%20Gemstones.json
Which includes customProperties
mixed with itemEntry
and variant
generation.
Clock the hasRefs
flag.
Basically this one '''item''' explodes to 46 items on the site
See video:
https://github.com/ebullient/ttrpg-convert-cli/assets/52298102/9a0a3e25-8329-413e-aeee-f88c3a14693b
I have a homebrew that has a couple of custom properties for items. I would like to include these in the template.
Hamund's Herbalism Handbook
Here is an example of an item with these properties:
Hamund's Herbalism Handbook