-
-
Notifications
You must be signed in to change notification settings - Fork 33
Estimation Settings
The label of the rule. If left empty, it'll show the index number of the tab.
You can set up your own custom rules with a javascript conditional, like checking for actor types, items, effects, etc.
Actors in a system that have "creature types": actor.system.details.type.value === "TYPE"
(dnd5e example)
Example: undead, ooze and other creature types that don't bleed.
For creatures with a Custom Type, target
actor.system.details.type.custom
instead.For a specific subtype, target
actor.system.details.type.subtype
instead.
Actors with a certain an item: actor.items.find((item) => item.name == "ITEM NAME")
Example: A feat that sets how a character's health works.
Actors that have an effect of a certain name: actor.effects.find((effect) => effect.label=== "NAME")
Example: An effect with a specific name, such as "Stable" or "Sleep".
Actors that have an effect that set them with the the Unconscious status effect: actor.effects.find((effect) => effect.statuses.has("unconscious"))
Example: specific estimates for a set type (e.g.
actor.system.type === "undead"
), or creatures affected by an item/effect/feat, etc.
Important
Please, don't open issues to request guidance on how to write these, use the discussions or ask around Foundry's #macro-polo channel on Discord.
The Ignore Color option is a way to set up custom rules that will use the color logic of the next valid estimation for the token. Its use-case is for when a specific effect should take precedence over the current health state of the token.
Note
The only systems that have these by default are the D35E and PF1 systems.
Remove the estimate at 100% and leave the last estimate at 99% maximum.
You don't need to rearrange the values when adding a new estimate to be in-between a range, they will get sorted automatically once you save the list.