Autoexplore, exclusions, and transparent walls
Posted: Thursday, 29th September 2016, 17:56
So I saw Psyche, but didn't wake her up. Set an exclusion, backed away, with Psyche still asleep. Autoexplore brought me close to the explored area again from a different angle, and automatically removed the exclusions because it thought the area was safe, as a wall separated the exclusion mark. However, this wall was transparent; autoexplore brought me back into view of Psyche (through the transparent wall) and she woke up and came after me me.
I took some screenshots, which should help to clarify the issue:
In the above image, the thicker red X marks where Psyche had been asleep, and where I placed the exclusion (directly on her). Autoexplore brought me back around to the corner, which it thought was safe and automatically un-excluded. And it would have been safe, except that the wall was see-through, and Psyche (plus an Ogre) saw me.
As I tried to retreat, I ended up in this situation:
Now, I had a teleport scroll so I got out of this safely, no big deal, but I assume this is buggy behavior. And I imagine there are other cases where something like this happens.
I'm not too familiar with how autoexplore and exclusions work under-the-hood, so I'm not sure if this is a simple bug to report (via Mantis) or if this is a known issue that is difficult to fix. I imagine there are other similar cases that result from poor interaction between autoexplore and exclusions, so I'm posting here to raise the issue and generate some discussion.
I took some screenshots, which should help to clarify the issue:
In the above image, the thicker red X marks where Psyche had been asleep, and where I placed the exclusion (directly on her). Autoexplore brought me back around to the corner, which it thought was safe and automatically un-excluded. And it would have been safe, except that the wall was see-through, and Psyche (plus an Ogre) saw me.
As I tried to retreat, I ended up in this situation:
Now, I had a teleport scroll so I got out of this safely, no big deal, but I assume this is buggy behavior. And I imagine there are other cases where something like this happens.
I'm not too familiar with how autoexplore and exclusions work under-the-hood, so I'm not sure if this is a simple bug to report (via Mantis) or if this is a known issue that is difficult to fix. I imagine there are other similar cases that result from poor interaction between autoexplore and exclusions, so I'm posting here to raise the issue and generate some discussion.