Mushano Posted Monday at 11:11 PM Posted Monday at 11:11 PM (edited) On 6/8/2026 at 7:59 AM, hextun said: Before going to "save is borked" instead of "hextun made a booboo", given that I *did* elect to move *away* from actual API calls because in *my* testbed the API calls were not working, I'd like to collect a little info if you don't mind. Hmm.. is this a purely custom modlist, a pre-made modlist (e.g. from wabbajack), or a customized pre-made modlist (e.g. from wabbajack, but with your own tweaks)? I'm curious to match it against my own testbed for SLP+ (Masterstroke) Do you have an older save you could load, verify things are working (since you did feel confident things were working at one point), and then try 980 again? Are you willing to do unpaid testing? Side note/PSA: In the LL text editor (i.e. where I am typing right now), if you enter a smiley (like colon-right parens, i.e. ":)" ), but do not hit enter or space after the parens, your arrow keys will stop allowing navigation in the text editor until you do so? Like, start typing, then enter the ":)" but without the quotes. Then, before you hit enter or space (thus letting the editor convert it to the icon), try using your arrow keys. You can't! This surprised me. Enjoy! Purely custom modlist before wabbajack existed! Basically a migrated Skyrim to Skyrim Special modlist using Wrye Bash and not any Mod Organizers. I could try older saves, but this behaviour seems kind of familiar to an old version of SL triggers where for some reasons things would play out of order. Like start of sex scripts wouldn't run, but it would fire orgasms or end of sex scripts. Or end of sex scripts would fire at the beginning of the scene. Not sure what fixed it. I could definitely try some save files and see what happens. I hope we narrow down the problem. PS: About the smiley problem. Nope! I do not have that problem . Actually I just got that bug too. Most of the time I can, but if I enter the smiley mid sentence, like I'm editing a sentence, I ran into that bug. For reference, using Firefox. Edit: Okay. Testing done. It seems like somewhere in-between 980 and 983, that's when the logic broke. I'm not 100% certain, but 982 worked most of the time, so it might just be 983 that is broken at the moment. This was tested using an older save that I had near the beginning of my game. Testing newer save seems to confirm that 983 is currently broken with SLP+ and aggressive detection. Using a newer save, it does seem like 982 works, but 983 doesn't. Edited 14 hours ago by Mushano
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now