Awesome find, and once again I appreciate the fix + the logic behind it. Fix applied for v0.9.8
Found and tracked down another bug. Milking gets applied multiple times during group sex. Every milking action milking is applied to every lactating character milked times the number of lactating characters getting milked. So if 3 lactating characters get milked during group sex, they each get milked 3 times for a total of 9 milkings. This is not dependent on the number of people doing the milking, just the people getting milked. Anyway, too much milking and too much text spam. Milking can also currently give weird negative values. The fix is to move the milking logic outside the for loop it's in. I moved it to before the for loop. I also made various changes that made sense to me and fix some aberrant behavior. The code is too long and complex to paste it here without formatting so I put it on pastebin together with lines at the start and end of it which indicate where I placed it in newsexsystem.gd and my comments: https://pastebin.com/VpdqGgJ6
The old milking code and my comments should also be removed before applying this fix. Just in case someone wants to apply my fixes themselves.
Edit: I'm also getting some errors with jobs. Seems like something connected to the guardian job? I'm running a 9.5 save on a fresh 9.7 install based on 5.25. I'll see if I can track it down but my console log is this(ignore the kennel error that is the mod overwriting one of my fixes from before :P):
Okay, I've found the reason for that elusive error I posted about before. It has nothing actually to do with the save. I checked and the job exp and all that stuff was already present on the save. I already had saved it in 9.7. The real reason is that the random events for guardian and slave catcher jobs use the global.evaluate function which relies on the global.currentslave variable. gloabl.currentslave however is only set when the slave tab is opened(the slave which tab it is) or in sexuals.gd on a few occasions. This means that the slave data used in those random job events is the data for the slave which had it's slave tab opened or had sex most recently. This is bad enough as the wrong slave's data is used, but when the game is started freshly and a save is loaded where a slave is assigned to either guardian or slave catcher jobs then the day is passed without doing anything else the game will generate errors in the console as the global.currentslave is nil/null and no end of day report is displayed.
I uploaded the needed changes to jobs&specs.gd to pastebin again: https://pastebin.com/DnjJvAnG