"Sacrificial Bloodlines" bug

[deconite]

During the quest "Sacrificial Bloodlines" when I choose to 'attack' during the conversation that starts the quest and then kill everyone combat does not end.  Someone named Lliras walks in 'nods', I get "nameerror" in the combat log and combat continues despite the fact that he's not hostile.  I've reloaded and this happens no matter what responses I choose between starting the conversation and picking 'attack'.

 

 

 

I was unable to compress either my savegame or the output log to less than 507 kB

 

[Giskler]

Same problem. I killed Lilras before at the house and now every time I try to kill Sinnoc the game gets stuck in combat forever. Even handing in essence potion and then attacking him results in the same situation.

Edited March 30, 2015 by Giskler

[omegabet]

Same here. [The workaround I posted here does not work, I deleted it]. I will try different workarounds later and have to get the the essence first.  

Edited April 1, 2015 by omegabet

[Oscuro]

I'm following up on this issue and would very much appreciate additional information (e.g. save game files and output logs). It would be awesome if you could, please, provide any of that.

 

The errors where events fail to fire at the end of encounters are notoriously difficult to reproduce and we're looking into any possible causes. I'm wondering, have you tried uninstalling the game and trying your backed up save games after a new install?

 

Thanks for your patience, guys!

 

Jorge

[bokruse]

I had the same experience. It may be unrelated, but I did notice that he showed up while I was technically still in combat, having killed most including the leader, but there was 1 npc left around the corner from where I was. 

[akibaru]

I had the same experience, but after a couple of minutes in combat I discovered there was a lonely enemy fighter in the western side of the house that didn't engage when the fight started. Killing her solved the issue for me.

[reclinemusic]

I had the same experience, but after a couple of minutes in combat I discovered there was a lonely enemy fighter in the western side of the house that didn't engage when the fight started. Killing her solved the issue for me.

this fixed it for me