That is how I thought it would look but does that change anything else about my post? I still think it would "hurt" the writing if for example: only have sex with girl at the bar yet (somehow) finds out and acts the exact same as if you fucked someone "closer" to her? Or even worse (for her character) she "lets" you cheat one, two,three, however many times before she's says "hey i wanted honesty!".
IMO HanaCheat "punishing" you at +1 or above (sometime down the line) makes the most amount of sense "in story" and its HanaCheat instead of HanaCheat(X) because there are so many opportunities to do it (but any will result in the break up or whatever).
Edit: You can also use URM to view and modify variables without needing the rely on the walkthrough (you might lose context as to what the choices do but it's easy to figure out)
Like I said, all I know is this is the direction TD&GIL went with instead of "HanaCheat=True" or "HanaCheatVeronica=True", so their plan doesn't involve a "one and done", nor a "I can't believe you cheated on me with Veronica" scene when the blow-up finally happens. There's the small possibility that it is a "one and done", and they want to have Hana demand MC tells her how many times he's cheated, but to me that seems like extra work on the code to modify a single line of dialogue. Remember, the more characters, and variables, and queries you put in your code, the harder it has to work, and the greater chance for bugs to occur, so their variable title/math choice tells me that the blow-up scene will be branching scenes rather than "you made one choice, here's the exact same scene for everyone who made that choice regardless of frequency."
I referenced the walkthrough as the Mod only gives you the path you're on and whichever you pick of A) Veronica, B) bar girl, C) Rosalind, or D) None, shuts out the other 3 paths, so you don't know those options even exist, much less if they also give the "Hana cheated" variable unless you either play all paths or check the walkthrough.
