- Nov 18, 2016
- 4,398
- 10,344
All good. These things happen, I myself constantly change old code as I learn more.bobdillan! You're a legend. I had no idea there was something like that, it all was very confusing.
Glad the mystery got solved. Thanks a lot for looking in to the code. Cheers!
I'll look in to a switch kind of thing, no idea how I go about that as of now, but I'll figure it out.
I'll edit the thread to make it clearer for returning players.
As for a NTR switch, you could do something like a NTR boolean variable. Where you would do something like $ nTR = True or $ nTR = False
And when doing a check you simple have If NTR, if true it executes if false it passes or goes to the else statement if you have one. Well that is how it should work with python, I myself am still largely unfamiliar with ren'py so it may work differently.
As for the idea of having a check that works both for new and old players (say if you change the old code to use this check).
You could have something like an event for when the player wakes up (like you have the other events trigger), that uses a ntr_check variable, where if false it will ask the player if they want to go the NTR route or not, and then setting the state of the nTR variable.
As for new games you would automatically set the check to true after you ask the player when they start (just be sure not to have it in the if or else statement).
Of note though this would lock the player into all NTR or all non-NTR paths, and wouldn't give freedom to choose indepentantly so may not work with how you want to do the story.
haha, thanks for the praise, but to be honest I am more novice-intermediate, I just knew that there was something to look for since I always play non-ntr. and have a bit of experience using the ingame console to try and fix my old saves cause effort to restart if a big game. :SAnd added to dev notes/save file at the bottom of the thread.
Thanks a lot, bobdillan! I had no idea you were a code wizard.