Using Safety seems to disable trap location rendering even for following floors #18
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
In the newest version, using a pom of safety once stops the plogon from rendering traps on the next floors.
This behaviour did not occur using previous versions.
Noticed in PotD and EO so far. Have not tried HoH.
Oh I am not the only one. I was trying to figure out if there was a conflicting plugin but disabling everything else doesn't seem to help.
The plugin recognizes all other chat-based triggers, but not "Floor X" to reset the sight/intuition state.
If I write this as a test script, it shows the logic for creating the floor change regex is seemingly not functioning anymore:
Output:
Can confirm, I am also having this issue in PotD
Fixed as of v4.5. Not sure why this broke; it doesn't seem like the underlying LogMessage sheet has changed in any notable way.
This isn't really a change so much in the plugin as in one of the libraries used underneath, I think (version 4.4 has been out for 3 weeks).