Log in

View Full Version : [2LVL] in effect not working



SillyOldeBear
January 20th, 2024, 21:31
I am not sure if this is the right forum to post this, but I assume that this type of processing is game-system specific and the issue is in a Pathfinder Remastered campaign.

I am trying to add the effect for Kineticist Deflecting Wave feat (provides resistance equal to PC level for bludgeoning/slashing and twice PC level for acid/fire). I coded the effect as:


Deflecting Wave; RESIST: [LVL] bludgeoning; RESIST: [LVL] slashing; RESIST: [2LVL] acid; RESIST: [2LVL] fire

When added to the combat tracker for a level 1 Kineticist, it yields:


Deflecting Wave; RESIST: 1 bludgeoning; RESIST: 1 slashing; RESIST: [2LVL] acid; RESIST: [2LVL] fire

From my understanding, the computation is done as the effect is being added to the combat tracker, so this will not work correctly when the damage is applied.

Trenloe
January 21st, 2024, 11:29
This has been discussed recently in the Release 19 thread. The issue is when there is something after the [2LVL]. I'll get this fixed in a future release. In the meantime, as a workaround, use [2LVL], fire - i.e. put a comma after the ].

SillyOldeBear
January 22nd, 2024, 04:23
This works. Thanks!

Trenloe
January 22nd, 2024, 09:52
The issue is when there is something after the [2LVL]. I'll get this fixed in a future release.
It probably won't get fixed in a future release. The best "fix" would break data with a space - e.g. cold iron damage types. So the syntax going forward will require a comma.

Trenloe
January 23rd, 2024, 19:45
Or maybe it will...

Issue with extra effect data after [xLVL] entries has been fixed: https://www.fantasygrounds.com/forums/showthread.php?80142-Release-Updates-for-January-23rd-2024

It was deep within a complex regular expression - but the fix is pretty risk free for existing effects, so I got it updated today.

MaxAstro
January 25th, 2024, 04:40
Yay!