I remember I managed to cause this A LONG time ago in a purely vanilla game, and had no idea how or why it was happening, but either I started a new game and it was fine again, or it just fixed itself on it's own somehow after the fact because it wasn't doing that anymore, but strangely enough, I wanna know what exactly would cause that, just so I can MAYBE do it again at will because why not?
Interesting, so it's not an issue specific to the mod but rather a rare occurrence in the game itself. It seems like it would logically be an instanced variable not getting purged but rather carried over to the next "combat" encounter (even consensual ones), but without looking into and familiarizing myself with the architecture of the game I can't do much besides blind guessing to figure out how or why it is happening.
So far I have tried:
Starting a new game, which "solved" the issue, indicating that the source of the problem must indeed be in the save file rather than the browser cache.
Simply continue playing to see if the issue resolved itself. I progressed until the start of December, but the issue persists (so as funny as it would have been, it seems "No Nut November" is not to blame).
Some light save editing. I examined the save file myself and noticed variables "enemyarousal" and "enemyarousal1" through "enemyarousal6" were all set to "99.168666666666681", which seemed odd given that "enemyarousalmax" was set to 5. I tried setting all the enemyarousal values to 1, but NPCs remained on a hair-trigger when loading the game to test the edits.
Attaching another (unedited) save from the start of December, because... well, why not.
UPDATE: Tried doing the save editing above in different circumstances, namely while out and in of combat, to no avail.
