Releases: devakm/gurps-traps
Release list
switching to DetectTraps configuration in macros
In V12 MATT does not support running Chat Message as TriggeringPlayer. This means bad things for ease of configuration, not just for this module but for any module.
I have created a ticket with IronMonk about it, but have not heard back yet, so for now I am assuming there will not be a quick fix.
If you and your players don't mind having the GM make all rolls for the player, then you can stick with the original easy configuration method: just put it in the chat message. This worked fine in older versions of MATT and Foundry.
This is what I mean by easy:
All the trap details are defined in the chat message, which means it can be saved in the Tile Template. The problem in V12 MATT currently prevents this from working unless the GM makes all the rolls.
For me, having the GM make player rolls is a terrible player experience, but all the alternatives are bad.
Run Code sounds like it should work, but seems to again only run as GM.
The only other option that does what we want is Run Macro, with Use Core Macro Execute enabled in MATT Config. If you don't specify Use Core Macro Execute in MATT Config, you will get strange results (some rolls will be forced to the GM).
That macro contains the same command that the Chat Message use, just wrapped in JavaScript:
let OtF = `/:DetectTraps title="AlchemistFire" dice=4 adds=4 type=burn rsize=3 attrib=DX difmod=-6 skill=Jumping detectwith=!PER! detectdif=-8 tag=BXTrapStatue05`;
GURPS.executeOTF(OtF);Configuring each trap to actually run as TriggeringPlayer requires this extra step (creating the above tiny macro for each trap.
Over time this may lead to a clutter of small macros, so bury them in a folder out of the way. Hopefully we'll have a better solution in future.
0.2.3 YellowMold
What's Changed
Full Changelog: 0.2.2...0.2.3
cleanup documentation
Cleanup and documentation
Merge pull request #12 from devakm/v3 V3


