 |
The builder is the only guard using "reattach" to switch the weapon to different joints. The rest still use the old system where the sword is attached to the same joint all the time (and still have all the problems associated with that). The mystery is why does reattach work fine with the draw animation to move from back to hand, but not work with the sheathe animation to move from hand to back? It should be exactly the same code. My theory on the forums is that something might be cutting the sheathe animation short and forcing the reattach to happen before the animation moves the weapon to the correct position. This could be tested by alerting AI, saving periodically while you wait for them to de-alert, getting a save right before they try to sheathe the weapon and then watching them sheathe it several times in slow motion (using g_timescale 0.3 or some number less than 1) or stop-motion using g_stoptime 1/0 |
|
|
This is hard to test because a lot of the time they aren't sheathing the hammer. I know they won't sheathe it if they've "seen evidence," but I think there's also a bug involved, because I saved right before he sheathed it, then restored, and on the restore he never sheathed it. I was testing by shooting a noisemaker arrow into a dark, inaccessible place, so that hopefully they would never register "seen evidence" to tell them not to sheathe the hammer. But I only ever saw a sheathe once (and yes it did become bonerfide). There is probably a better way to test this, like script a builder guard to alternately play the draw and sheathe animation forever. |
 |
I seem to recall fixing that long before 1.00. |
- Anonymous
