Dorn Stutter After Killing Kryll

Sam_

Dorn is in one of those start to try to talk every few seconds but stops type of stutters, preventing him from walking more than a couple of feet before stopping. It started in area AR5500 right after I killed the Necromancer (was it Kryll?).

Looking at Variables:

DORNCDEV=1
DORNEXISTS=1
DORNINTERACT=1
DORNPARTY=1
DORNPLOT=3
DORNTIMER1=1475827
DORN_AMBUSH=1
DORN_ROMANCE1=1137066
KRYLLDEAD=1

Expected behavior: this shouldn’t happen. If there is any other information needed to diagnose the problem, let me know. So far I haven’t been able to discern exactly which block in Dorn’s script is causing the hang.

EDIT: Game version is v1.0.2007

EDIT2: The offending block in DORN.BCS is block 22:

IF
Dead("KRYLL")
GlobalLT("kryll_conv","AR5500",2)
!ActuallyInCombat()
THEN
RESPONSE #100
StartDialogueNoSet(Player1)
END

Bomimo

and i can't quicksave, rest or move two feet without him motioning towards the PC as if to talk. Is there a command to stop him doing that?

Bomimo

For the sake of this getting solved, uploaded the two savegames in question here: http://www.mediafire.com/?ak2m60s6503n30n

The problem is that we just killed Kryll and the following dialog had played. Once it was done, he keeps actioning towards dialoge, but nothing comes. Both my PC and him are inactive and spazzing out.

Avenger_teambg

This was reported already in numerous times (even in beta).
@Tanthalas please merge with : http://forum.baldursgate.com/discussion/8997/dorn-stutter-after-killing-kryll

The issue is in the bugtracker at least twice too.
Here is the fresh one: http://support.baldursgate.com/issues/1010

Bomimo

Aha. Okay. I should point out that booting him back to Friendly Arm fixed the issue.

Avenger_teambg

That might be a good workaround until a fix, yeah.

Avenger_teambg

I think i can fix this...

KeithS

@Sam Will be fixed in the next patch. Looks like when the player grabbed the note it would play the "let me see that note" immediately skipping the "see you suffer" lines. Unfortunately, that caused some necessary variables to not get set properly. That shouldn't be able to happen now.

Sam_

@KeithS Cool