chasing enemy when teleported out of sight

jolly_bb

i'm not fully sure this is a bug, although to me it certainly seems so.

first observed while fighting phase spiders: charname was doing recon while rest of party stayed by the edge of the map. some phase spiders attacked charname on the far end of the map, but unespectedly teleported also beside the rest of the group. like they would have a godike knowledge on where to look....

this actualy works both ways: when i attacked devaeron my charname knew exactly where to run and attack despite the mob teleporting way out of anyone's sight. in effect charname was running room to room chasing down devaeron after his every teleport, and always to correct room

i don't recall experiencing this pre 1.2 but i can't verify.

so:
CURRENT BEHAVIOR: both party members and enemies will continue attacking/chasing the adversary despite the latter vanishing out of sight. phase spiders are able to locate and attack (teleporting in the sweet spot) the party members they have no sight or knowledge on

EXPECTED BEHAVIOR: when a character (either we or enemy) goes out of sight into fog of war, neither party memeber nor an enemy should have inherent knowledge on where to chase and attack this character. phase spiders should not have knowledge on party members they had no chance to witness - thus should not be able to teleport to them and attack.

NOTE: this is on iPad, not tested on PC

Tresset

Huh? I could have sworn that anyone that moves out of the line of sight of the party can no longer be targeted by the party... I will look into it later...

Emptiness

This sounds similar to other reported bugs, such as enemies continuing to follow their target after it becomes hidden or invisible, and Beholders attacking enemies out of line of sight. I don't know if it has been determined whether they share a related cause, but I suspect that they do. It seems to me that when the game engine is making automatic decisions for an entity it is using information that it has but which that entity should not have. That would explain a number of bugs, including this one.