Type:
Severity:
Game version:
Concerns:
Found in Version:
Status:
Identifier:
Name:
Description:
When leaving "Imperial Commission" in Andothren durring the TR Andothren mages guild quest "cell bound" https://en.uesp.net/wiki/Tamriel_Rebuilt:Cell_Bound after freeing the target of the quest "Samay" 3 Camonna Tong thugs confront you. If you choose to fight rather than pay or leave him to his fate, they immediately turn aggressive and the error message in the screenshot appears:
"ArrowBone missing on actor "TR_m4_q_Nadene Drin00000000"
Continue running executable?"
selecting yes and continuing does not seem to have any issues aside from the annoyance caused from repeating the event over and over because the guards join the fight on the side of the thugs.
There is a single guard on top of a tower nearby, and if Samay or any of the thugs move more than 5 feet in that direction, combat initiates with the trapped guard who can't reach us to attack. After killing the thugs, Samay then charges over toward the guard tower, which then aggroes at least one other guard (the one patrolling on top of the hill behind the tower who gets stuck repeatedly on things trying to reach Samay, and combined with the guard on top of the tower left me extremely confused who/what was trying to kill us) and occasionally also aggros the guard patrolling near the mages/fighters guild.
Guards can be killed without a bounty, I don't fully understand the mechanics of when a bounty is applied, but I assume it is related to them joining combat with the aggressors. Chasing Samay across the city as he tried to commit suicide by cop and got stuck and fell into the canal repeatedly was not an enjoyable experience.
I am assuming this is not intended behavior given the positioning of the guards (one on top of a tower roof and the other behind fences), and the fact that Samay is charging across the map and through the canal.
Comments
So this is two separate
So this is two separate issues.
Issue 1 is now fixed in the
Issue 1 is now fixed in the latest TD_Addon.
As far as 2 goes, I couldn't reproduce it, so unless another quest dev has more luck, I'd suggest to close this report.
Closing as 1) was fixed and 2
Closing as 1) was fixed and 2) hasn't been reproduced. Most likely it's some sort of mod conflict.