So currently persistent damage in this module is an effect with some flags to contain the data used for identifying persistent damage. This was the quickest and easiest way to implement it, but it is alien to the core system. This will cause problems trying to fit it in with afflictions and fast healing, so trying to make a roadmap for how it would be handled.
So in pathfinder's rules, persistent damage is actually a "condition", curses/poisons are "affliction", and fast healing is its own thing. Condition is something already in the core pf2e system, but conditions in core will eventually be replaced by effects. Since everything will be an effect (perhaps with subtypes like condition), the questions become the following:
1) How will stacking/stages work? Afflictions are somewhat like status based conditions except they have a different effect per level (sometimes an instantaneous effect like damage). It is likely that effects innately will need some ability to stack, and event stacking will need to be handled in core.
2) How will editing params for persistent damage like DC/damage work? Effects are currently kinda clunky to edit, but there apparently is UI being planned for them. How will that UI be accessed if rules are disabled? Should users have access to EVERY rule? If they remove every rule from a condition typed effect, is it even a condition anymore?
3) How will ensuring that conditions aren't duplicated work (so that they stack properly?) Will there be a manager to ensure uniqueness? What happens if a user edits the condition effect rules?
It seems that for a condition to be implemented as an effect, it will need some way of defining certain parameters as read only, and certain parameters are not read only (like persistent damage type would be read only, but DC wouldn't be since those can actually change on some creatures).
So currently persistent damage in this module is an effect with some flags to contain the data used for identifying persistent damage. This was the quickest and easiest way to implement it, but it is alien to the core system. This will cause problems trying to fit it in with afflictions and fast healing, so trying to make a roadmap for how it would be handled.
So in pathfinder's rules, persistent damage is actually a "condition", curses/poisons are "affliction", and fast healing is its own thing. Condition is something already in the core pf2e system, but conditions in core will eventually be replaced by effects. Since everything will be an effect (perhaps with subtypes like condition), the questions become the following:
1) How will stacking/stages work? Afflictions are somewhat like status based conditions except they have a different effect per level (sometimes an instantaneous effect like damage). It is likely that effects innately will need some ability to stack, and event stacking will need to be handled in core.
2) How will editing params for persistent damage like DC/damage work? Effects are currently kinda clunky to edit, but there apparently is UI being planned for them. How will that UI be accessed if rules are disabled? Should users have access to EVERY rule? If they remove every rule from a condition typed effect, is it even a condition anymore?
3) How will ensuring that conditions aren't duplicated work (so that they stack properly?) Will there be a manager to ensure uniqueness? What happens if a user edits the condition effect rules?
It seems that for a condition to be implemented as an effect, it will need some way of defining certain parameters as read only, and certain parameters are not read only (like persistent damage type would be read only, but DC wouldn't be since those can actually change on some creatures).