if you asking about the URM interface - some games (very very few) do change the ui text size - especially games with higher resolution than 1920x1080
its null hypotesis, its already fix itself for unknown reason,
"This error" isn't really useful, please see the OP on how to report a bug:
$ testtuple = (1,2,3)$ dictttuple = { "a":: (1,2,3) }$ dicttuple = { "a":: (1,2,3) }$ dicttuple["b"] = (4,5,6)
I think the problem here would be defining what a simplified code path should look like. Not every VN uses affection systems, including the big one DDLC (pretty sure at least. Linear and purely choice based game).
That's as simplified as that particular game's code is going to be able to manage. Automated tools like URM are going to need to have a specific criteria for what they include or don't include, and since every game dev may do their game's important variables completely differently, URM's trying to do its best to show you what appears to it to be relevant. If you have ideas for specific filters/criteria for what shouldn't be considered relevant, call those out.
[girl]_relationship instead (and on one branch, unlocks a gallery scene in persistent, unlocks an achievement, and increments the game's harem size counter). So should it not include string variables? Should it not include the harem size counter variable? How does URM know that the haremcount variable isn't a girl relationship variable? On top of that, variable names are almost infinitely variable, completely up to the dev, and can be almost anything. If the dev wanted to (though I pray they don't), these variables could have been quite literally all gibberish, and it would work the same as long as they were used consistently.persistent.g_iris_02a gallery unlock variable or the unlock_achievement call or not, but people who do care about 100% completion very much want to see those to know which choice leads to the sex scene/unlock and which doesn't.
I understand your argument but this is what it looks like on a pre-2.3 version. Perhaps this wasn't the best game to show this example but I feel there is a middle ground, no? Even cutting out all the #Some dialogue would make it much more legible. I haven't struggled understanding my decisions on most any game with any version of URM, until now. Also look at another example below, the codepath shown is only half of how long it actually is! I would just revert back to an old version but the ignore variable option was introduced in 2.5 and now my saves in this game wont work with older versions of URM.
Perhaps this game is worse than others but regardless it makes the choicepath essentially pointless.
i find it massively helpful to know what i get into when i make a choice and what effects them
I don't disagree that it can be helpful, but it can also be a hindrance. It would be cool to continue having the new features as URM gets updated with an option for the same codepaths we had pre 2.3.
With all of the conditionals in the current-URM example, the older version of URM is not giving you accurate or complete information for this game particularly.
lea_hug == True. Nothing else. It wouldn't even mention lea_relationship at all, since that's behind a conditional statement (and the current implementation in URM even tells you whether that condition is met), but the more detailed version lets us know what the conditions for it are.
if persistent.lang == "english":
menu:
"Letting the slave cum in Oscar's mouth." if True:
$ fmc_bi_cuckold = True
"Stop the slave from cumming and kick him out" if True:
pass
elif persistent.lang == "russian":
menu:
"Позволить рабу кончить в рот Оскара" if True:
$ fmc_bi_cuckold = True
"Запретить рабу кончать и выгнать его" if True:
pass
scene scene_120_09
with Dissolve (1.0)
e_narrator "After falling exhausted on the bed, [fmcName] looked at the slave and said"
narrator "Обессилено упав на кровать, [fmcName] посмотрела на раба и приказала"
if fmc_bi_cuckold:
e_fmc "Take off the condom and cum in that worm's mouth."
fmc "Снимай презе