-edit-
It's not guaranteed your game has that setting in script.rpy. It could be in the whole project, so you're better off searching for those lines while searching the whole project, which is possible in pretty much any software, including Notepad++.
He don't even have to bother with this.
First, creating a "rollbackRestore.rpy" file:
Python:
init 1000 python:
config.rollback_enabled = True
config.rollback_length = 50
config.hard_rollback_limit = 50
def block_rollbackTWEAKED():
pass
renpy.block_rollback = block_rollbackTWEAKED
Then, dropping the file in the directory named "game", where the rpy/rpyc/rpa files are located, should be enough for 99% of the games.
This being said, nowadays it's exceptional that a dev mess with the rollback without reason.
Most of the time, it's done to counter a bug that the dev haven't been able to fix. Like by example those who've message discussions embedded a screen, and trigger the whole discussion with a single
show screen
, or things worse than this.
Therefore, restoring the rollback then using it can highly broke the game.