What you're talking about is definitely possible, Ren'Py just uses python for the most part, and python is versatile enough to do this.@DarthSeduction
See, this is what I was thinking; an adaptive code that corresponds to certain triggers. Of course, I don't know Ren'py coding and therefore don't know if it's possible or the potential complexity of implementing it, but I used to make Flash games many years ago and some included adaptive code that allowed the dialogue to correspond to user input names and choices. It's been awhile since I did those games (I made them in college) so I don't remember the exact code used, but I basically set up different code references that would refer to certain characters and objects in specific ways and then applied those to certain characters so the dialogue made sense.
To use Summertime Saga as an example, there could be several different references for Debbie/the Mom (bearing in mind I don't know how Ren'py coding is written, this is just how I could imagine it in a basic sense);
I realise this is a very complex idea (and I realised it even more when I started typing this because I clearly hadn't thought it through, lol) especially since the same sort of thing would have to be applied to Jenny, Diane, and to Mrs Johnson and Eric, but if this were possible it still, in my mind, could perhaps better allow for the dialogue to still make sense and have a good flow to it without having to dumb it down and make it more simplistic and basic like some other games out there.
- Deb = Name of the character either input by the player or the default name.
- E.g. "Mrs Johnson: Hey [Deb], how are you?" = "Mrs Johnson: Hey Debbie/Jane/Holly, how are you?"
- DebR = The relationship of this character to the MC.
- E.g. landlady, foster mom, Dad's friend, etc.
- DebR2 = A specific relationship of this character to the MC that is input by the player which overwrites the DebR reltaionship, i.e. Mom [D1], Mother [D2], Mum [D3].
- E.g. "my ([DebR] or [DebR2] if [DebR] = (D1), (D2), or (D3))= "my landlady/Mom."
- E.g. "our ([DebR] or [DebR2] if [DebR] = (D1), (D2), or (D3))" = "our landlady/Mom".
- E.g. "your ([DebR] or [DebR2] if [DebR] = (D1), (D2), or (D3))" = "your landlady/Mom".
- E.g. "their ([DebR] or [DebR2] if [DebR] = (D1), (D2), or (D3))" = "their landlady/Mom".
- E.g. "his ([DebR] or [DebR2] if [DebR] = (D1), (D2), or (D3))" = "his landlady/Mom".
- E.g. "MC: I love showering with you ([Deb] or [DebR2] if [DebR] = (D1), (D2), or (D3)) = "MC: I love showering with you Debbie/Mom."
- DebMy = Inserts the word "my" for parts of the dialogue where it needs to precede the relationship if the DebR2 condition has been met for the dialogue to sound more natural.
- E.g. "MC: I can't believe that ([Deb] or [DebMy] [DebR2] if [DebR] = (D1), (D2), or (D3)) just did that!" = "MC: I can't believe that Debbie/my Mom just did that!"
Also, it could maybe be made optional, as in when playing the game there could be 2 options to play; a "Regular Version" and a "Fantasy Version". The Regular one would of course be the one without an adaptive script/storyline and the Fantasy one would be, thus allowing people who don't want to enter specific relationships to not have to as there would a version of the game that is pre-set.
P.S. Again, I don't know Ren'py coding so this whole thread is probably just me talking out of my ass because I'm still bitter about the rule changes.
What this doesn't solve is the problem of the story not making sense outside of the perfect context. If you input landlady and she says:
M "Why is it that every time I see MC I start to feel the need to scratch an itch in my pussy? He's my Tenant! I shouldn't be thinking of him in this way."
Why should she care what she thinks of her tenant? Is there something wrong with a landlord having sex with her tenant? Why? The only way I can see that this would actually work is if you created multiple versions of every scene. But the titles given to other characters create an infinite number of variables, eventually you'd be forced to make at least a large portion of responses come out to a single generic version of the script. The question then becomes, how to you keep the incest ones from being routed to the generic script while not defining them in a way that Patreon would have a problem with?