[Pf2e] Inconsistent spot behaviour

[weepingminotaur]

For the past few weeks, I've been having some consistent issues with Perceptive that I'm having trouble reproducing. First, it frequently doesn't "pick up" Seek rolls and register them on the Perceptive token input for the purposes of finding things. This may be an odd interaction with Rezyor's Pf2e Additional Automations module, which auto-rolls a Perception check whenever the Search activity is turned on. The first time a player Searches (and triggers a Seek check), that check is often not picked up by Perceptive.

Last night, I test-rolled a check from a player token and all of a sudden it "found" hidden items on the other side of a scene, way out of range (I set the normal search range at 10 feet and the item was in another room the party hadn't even visited).

I'm happy to do further testing, but I wanted to bring these issues to your attention in case you can recommend next steps.

[Saibot393]

Ok, this is strange. I will do a bit of testing and see if i can find the cause.

[Saibot393]

I did a few tests and could so far not replicate the behaviour. Few questions to narrow down what could cause the bug:

• This is the module you mentioned, right?
  • If so, could you sned me the modules setting exports, maybe it some very specific interaction
• Do you have perceptives "Use Pf2e rules" activated?
• Were you using the seek action or did you roll perceptive from the sheet?
• What kind of objects were you using as the target of the seek action when testing
• Could you send me a screenshot of your perceptive range settings
• Could you activate the debug console output ( CONFIG.debug.perceptive.SpottingScript = true ), and send me the console output when using the seek action/rolling perception (probably something titled perceptive: Range Check AP and perceptive: Infos AP)

[weepingminotaur]

• The module is Reyzor's Additional Automations module, which is behind a Patreon paywall. I will send you the exported settings.
• I do have Use Pf2e rules on.
• I believe Reyzor's module rolls Seek checks automatically, but I will verify that.
• Will send Perceptive screenshot and debug.

[weepingminotaur]

I've been testing for secret doors and secret loot actors, by the way. In the weird behaviour I mentioned above, players suddenly found a hidden loot actor all the way across the map when I rolled a Perception check for the actor (by clicking the dice in the Search activity).

[Saibot393]

The range part is actually the part of the bug i worry about most. I think the part where search rolls are not recognised will be relatively easy to fix, assuming it really is Rezyor's Pf2e Additional Automations. But the range one has me worried since all the required range settings and calculations are internal perceptive things, so another module should not have any influence here. I hope the debug console log can give me a clue here.

[weepingminotaur]

OK, so I'm not able to reproduce that range bug. Generally, I can't repro issues by myself -- it's in a session when all players are logged in that weird stuff sometimes happens. But anyway, here's a screenshot of Reyzor's AA module in action and preferences. As you can see, it rolls a Seek check initially. Then if the player wants to reroll (once active Perception has expired), they click the Perception effect (which turns into dice -- they can't see their own result, though the GM can).

[weepingminotaur]

Here are my Perceptive settings in screenshots.

[weepingminotaur]

Just ran the debug command you gave me and tried seeking, etc. Got nothing except a bunch of yellow warnings in this screenshot. And it works fine when I test it myself, which is super-weird.

[Saibot393]

Ok, that is indeed strange. When using Rezyor's module for the seek action, does a normal roll report card still show up in the chat? If so, could you enter this into the console Hooks.on("createChatMessage", (pMessage, pInfos, pSenderID) => {console.log(pMessage)}); and send me the output when using the modules seek action? I have attached a screenshot of how the relevant output information looks like in vanilla Pf2e: