The fundamental issue with loops is that it requires some form a loop trigger to indicate to the program when to do the loop, which means inserting a function to check on variable update, or on time advance, etc...."is this variable locked? yes/no. then do this, else do this" which brings me back to my original problem of having to modify the script.rpy to include function trigger and having to release a modified script.rpyc every time Vren releases a new version. If thats the route you wish to go with it, then by all means, I was simply trying to figure out a way to ideally accomplish it WITHOUT altering the script.rpy. It's highly likely its not possible. I'm not a native python coder, I'm learning and adapting my syntax as I go, what can and cant be done, it's highly likely you know more than I do.
If this is the route you wish to go, then I would probably insert this loop into the change_arousal() function, that almost always called and used to modify both the player and all girls arousal values during sex.
On a side note, I just noticed the change_arousal function is defined twice in script.rpy. Im curious if there is a reason for this or if its just a bug. From what I've read, looks to either be a mistake, or a way to handle whether or not the script passes a logging boolean when calling the function.
Anyways, I'm going to wait until either a new SB mod version is released, or a there's been some significant content updates to the base game. I've messed around with a modded 13.1 version, made modifications myself (primarily to scene dialogue, creating new dialogue forks for opinion traits, for my own purposes
), and I'm very pleased with the direction Vren and the community is going with it. I cant wait to see what v1.0 will look like, and I really hope Vren eventually includes content from SB and other mods, once the core gameplay features are finalized, which I can completely understand that he should be more focused on establishing the core game mechanics before fleshing out content.
