-
Updated Today
- [ADDED][DCC] Attack tags - @ATK (#D#+#)
- [ADDED][DCC] Ongoing tags - DMGOE (# type), REGENE (#), TEMPO (#), TEMPOE (#)
- [ADDED][DCC] Damage/Heal tags - @DMG (#D#+# type), @HEAL (#D#+#), DMGDIE, @DMGDIE, DMGHALF, @DMGHALF, DMGMAX, @DMGMAX, DMGMULT, @DMGMULT, HEALDIE, @HEALDIE, HEALHALF, @HEALHALF, HEALMAX, @HEALMAX, HEALMULT, @HEALMULT (includes support for negative multipliers to convert damage/heal tags) (all multipliers support optional tags for <range>/opportunity/weapon/spell)
- [ADDED][DCC] Damage Adjustment tags - DMGWARD, ABSORB ([#Mult] type) (defender), IGNOREx (type) (attacker), MAKEx (type) (attacker), xTOx (type) (attacker) (where x = ABSORB|IMMUNE|RESIST|VULN)
- [ADDED][DCC] Ongoing Save tags - SAVEO (# type), SAVEOE (# type), FAIL (#, # end, encounter, # save type)
- [ADDED][DCC] Denial tags - NOHEAL (rest/hitdice/heal), NOREST (short/long)
- [UPDATED][DCC] HEAL effect now supports targeting
- [UPDATED][DCC] Attack/Damage/Heal rolls updated to show modifiers on separate lines for easier readability.
- [DEV][ADDED][DCC] Standardize damage/heal workflows for easier D20 implementation and maintenance.
Rulesets migrated: DCC, MCC, M&M, ALIEN, SYMBAROUM, VAESEN
-
Just a reminder that as reported in other threads, the release was delayed a week to give me more time to look at or help with extensions. If you have an extension and need help, please reach out to me directly.
In that vein, I am also looking at popular extensions reported on Discord.
I just pushed a Test build update for Aura effects (a popular third party extension no longer supported by the original developer); if I can get some people to help test it.
Regards,
JPG
-
Updated Today
- [ADDED][CoreRPG+] Targeted Effect Descriptors - self, !self
- [ADDED][CoreRPG+] Conditional tag operators - CONDITION, FACTION, NAME, RANGE, STATUS (Ex: CONDITION(blinded), NAME(Spider), RANGE(<=30), FACTION(ally), STATUS(wounded))
- [ADDED][CoreRPG+] Damage/Heal tags - TEMP, @TEMP, DMGR (# type)
-
Updated Today
- [ADDED][CoreRPG+] Misc tags - STACK
-
Updated Today
- [ADDED][CoreRPG+] Conditional AND and OR support. AND phrases are resolved before OR phrases. Commas in conditionals act like OR phrases. (Ex: IFT: TYPE(dragon) AND ALIGN(evil) OR TYPE(undead))
-
Quote:
Originally Posted by
Moon Wizard
Updated Today
- [ADDED][CoreRPG+] Conditional AND and OR support. AND phrases are resolved before OR phrases. Commas in conditionals act like OR phrases. (Ex: IFT: TYPE(dragon) AND ALIGN(evil) OR TYPE(undead))
Can you nest statements with extra parenthesis to control resolution? Not sure if such a use case would be needed, but...
i.e. Conditional (X OR Y) AND Z
-
There is no parentheses support. As mentioned in the notes, AND is resolved before OR.
For some conditional tags, they support "or" within their own resolvers. (Ex: TYPE(dragon,undead))
Regards,
JPG
-
I've pushed back the release date for these changes to 2026-05-05; due to the fact that I'm still working with a number of ruleset and extension developers to ensure a smoother release.
Regards,
JPG
