vmangos/core

🦂 [Bug] Shadowfang Keep - Sorcerer Ashcrombe script delayed

mserajnik opened this issue · 2 comments

mserajnik commented

🦂 Bug report - Dungeon

It appears that the script where Sorcerer Ashcrombe moves out of his cell to unlock the courtyard door can be delayed for some reason. I did Shadowfang Keep yesterday and it took around 3 minutes before he started moving after he exclaimed Follow me and I'll open the courtyard door for you. All the mobs around the area had been killed before talking to him and requesting to unlock the courtyard door, although I don't think that that is even a requirement; at least with the Horde equivalent NPC it's apparently possible to sneak by the mobs with stealth and have him unlock the door.

I am not yet sure if this always happens, but I will try reproducing it later (and record a video, if it happens again).

Expected behavior

As far as I know, he should start walking immediately after talking to him; see https://youtu.be/PQOifDDT6z8?si=oQ2t1xr6gKL2ff7U&t=499, for example. I can't find any information that suggests he sometimes might wait a while before starting to move.

Steps to reproduce

  1. Unlock Sorcerer Ashcrombe's cell door, talk to him and request to unlock the courtyard door
  2. Observe that he exclaims Follow me and I'll open the courtyard door for you.
  3. Observe that he doesn't start moving immediately after his exclamation; instead, it takes a few minutes before he gets going

Version & Environment

Client Version: 1.12.1.5875

Commit Hash: 13c4399

OS Client: Arch Linux (using Proton)
OS Server: Ubuntu 22.04 LTS

Crashlog

  • None
ratkosrb commented

I can't reproduce the issue.

mserajnik commented

I wasn't able to reproduce it either after trying a few times.

It could be that two players of the party managed to talk to him and request to open the courtyard door at essentially the same time (meaning, the second player managed to get his click through before the dialog closed for him due to the first player having triggered the script).

I have no idea if that could cause the observed behavior somehow, but I will try reproducing that situation later and report back.