Arelith

Description
==========
When scrying a target that is unable to be located for any reason, such as being warded, or them going through a transition, it triggers the 10 minute cooldown. I can't find my source, but this was confirmed to not be intended behavior, and until today, hasn't been a bug.

Steps to reproduce
----------------------------
Scry someone that produces the failure message, 'cannot be located.'
Expected result
-----------------------
Cooldown doesn't trigger, and scry can be immediately used for another target.
Actual result
-------------------
Cooldown triggers, and character is unable to scry as if they'd successfully scried someone.
Screenshot(s)
--------------------

Misc Notes
----------------

Which Server(s)?
------------------------
Guldorand
Gaming Platform(s)?
------------------------------
PC - Steam

I've had this same issue as well. Did not realize it was unintentional.

I always assumed this was intended. When they are not online, you don't get CD. When they are online and something prevents the scry you go on CD.

As someone making a completely uneducated guess I'm going to suggest that it's probably intended but undesirable. There was a dialogue change to try to cut down on how much a scrier learned ic when failing a scry. The new dialogue leaves it ambiguous to the scrier whether or not the target is warded vs. simply non-present for example. I think it could probably be intuited that the intent is one should follow the dialogue rather than the cooldown notification for gauging what their char learns but I do think modifying the cd to not trigger would make the situation less ambiguous at face value since there'd be no logical conflict of "Well why would my character think X if the cooldown only triggers in situation Y?"

perseid wrote: Mon Oct 24, 2022 11:58 pm As someone making a completely uneducated guess I'm going to suggest that it's probably intended but undesirable. There was a dialogue change to try to cut down on how much a scrier learned ic when failing a scry. The new dialogue leaves it ambiguous to the scrier whether or not the target is warded vs. simply non-present for example. I think it could probably be intuited that the intent is one should follow the dialogue rather than the cooldown notification for gauging what their char learns but I do think modifying the cd to not trigger would make the situation less ambiguous at face value since there'd be no logical conflict of "Well why would my character think X if the cooldown only triggers in situation Y?"

Correct! A few months ago, the feedback text and behavior was updated to be completely ambiguous in order to prevent metagaming.