![]()
|
|
Related Issues: 23162
After I had restored this property, Dreth's dialogue became completely broken.
Further investigations turned out that only one of the two topic info fragments - either the one on 0003D60C (this tocket) or the one on 0003D617 (ticket #23162) - should be allowed to modify the actor value. If both do it, the dialogue breaks.
Now to the decision which one to leave in and which one to remove: the topic 0003D60C (this ticket) is gender-specific, and its counterpart has a fragment that is correctly set up, with the actor value specified (i.e. that topic does already modify the actor value). For this reason, I restored the actor value on 0003D60C (this ticket).
Which means that the fix for #23162.had to be redone. To accomplish this, I did set the actor value to 'none' and compiled the topic info fragment down to a stub (since it would continue to spill errors if no actor value is specified).
Further investigations turned out that only one of the two topic info fragments - either the one on 0003D60C (this tocket) or the one on 0003D617 (ticket #23162) - should be allowed to modify the actor value. If both do it, the dialogue breaks.
Now to the decision which one to leave in and which one to remove: the topic 0003D60C (this ticket) is gender-specific, and its counterpart has a fragment that is correctly set up, with the actor value specified (i.e. that topic does already modify the actor value). For this reason, I restored the actor value on 0003D60C (this ticket).
Which means that the fix for #23162.had to be redone. To accomplish this, I did set the actor value to 'none' and compiled the topic info fragment down to a stub (since it would continue to spill errors if no actor value is specified).
Showing Comments 1 - 1 of 1