URM has to stop looking ahead at some point in the code and this makes the most sense.
The order is not set
Seems like they assigned something to Ren'Py's
Wouldn't it be possible to make smt like a variable change detection that we could turn on or off in the settings? It could appear like followed variables notif.
The main thing is, there will almost always be a jump to a different label. That's one of the fundamental basics of how Ren'Py works. Different devs order things differently, and while human brains can somewhat perceive "this is a completed conceptual 'scene'", code just can't (unless the original dev specifically coded their scenes to mark where conceptual scenes start and finish). On top of that, most games' devs are amateurs just figuring out how to code at all, so expecting any coding best practices from them is useless at best, and more often foolish.
Ooooh that's why I see some modders getting rly excited abt modding some well coded games lol. Honestly I don't know much abt code but I can understand the pleasure of decorating a clean and good looking place lol.
Kinda. Here's a few examples. I'm working completely off memory, so syntax might be slightly off, but this is the best way I can think of to explain the issue.
thank u. I pretty sure with this new information I can automate it with autohotkey
can't you just make your own mod file ie make a new text doccument and name it AutosaveKiller.rpy or something with
################################################################################
## Initialization
################################################################################
## The init offset statement causes the initialization statements in this file
## to run before init statements in any other file.
init offset = 99
config.has_autosave = False
config.autosave_on_quit = False
config.autosave_on_choice = Falseinit 99 python:
config.has_autosave = False
config.autosave_on_quit = False
config.autosave_on_choice = Falseinit 99 python:
config.has_autosave = False
config.autosave_on_quit = False
config.autosave_on_choice = Falseidk what to tell you i assumed one of those would work, all "init 99 python:" does is delay the game 'reading' the code block till after "init python:" and "init 1 python:"-"init 98 python:"
init offset = 99
define config.has_autosave = False
define config.autosave_on_quit = False
define config.autosave_on_choice = False
If you did search for "red sonata" you should have found 0x52's reply on this issue though...?! The game dev intentionally deletes any modification to the game, but 0x52 does mention a "workaround" for that -- I haven't tested it myself, so I can't tell if it's still working.
I actually didn't see that they posted a reply to that other post, sorry mate. Will try the workaround and see if that helps. Cheers.
game seems to run aggressive python scripting for anti-tamper? doesn't even want to run vanilla under sandbox environment (file access restrictions/networking blocked)
More specifically, Unity games don't follow a particular pattern like RenPy does, such as some specific, set variables and whatnot. You can't just pop a file into Unity and expect to be able to change a character's name or whatever, because that game might use its own code to make a VN, so you'd have to know that code specifically and target it. It's practically impossible to make a "universal" Unity mod that has a lot of the same high-level functionality that URM has, just because of that variation and the nature of Unity as a game engine. A Unity game can be anything, anywhere from a VN to the next Fallout NV, and because of that fact, no Unity mod can be as universal as URM.
