Store which params were used to generate .sav files #36

Open
opened 2013-09-22 18:58:43 +00:00 by kanzure · 0 comments
kanzure commented 2013-09-22 18:58:43 +00:00 (Migrated from github.com)

Not all .sav files are created the same. The decorator should save in a metadata file an entry about what parameters were used when calling a function. Then, when loading a save state to skip a function, only load a save state that matches the parameters. If that combination of parameters hasn't been played and saved yet, then play it.

There might be parameters that don't influence the save state structure, in which case, the skippable decorator should be given a list of which params don't matter.

@skippable(ignore=["some_param"])
def play_part5(self, some_param=None):
Not all .sav files are created the same. The decorator should save in a metadata file an entry about what parameters were used when calling a function. Then, when loading a save state to skip a function, only load a save state that matches the parameters. If that combination of parameters hasn't been played and saved yet, then play it. There might be parameters that don't influence the save state structure, in which case, the skippable decorator should be given a list of which params don't matter. ``` @skippable(ignore=["some_param"]) def play_part5(self, some_param=None): ```
This discussion has been locked. Commenting is limited to contributors.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
decomp/pokemon-reverse-engineering-tools#36
No description provided.