You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the repetition ID is based on the number of times a level has been completed in a run, but it doesn't give information about when in the run this repetition was played. It might be more informative to use the absolute order within the run instead.
That would require changes to :
bk2 filenames
events files
If we agree I can proceed with these changes.
The text was updated successfully, but these errors were encountered:
I think that when one is looking into the structure of a run, the event file is the best place to start with as it includes the timings too. In the event file you have the order of each repetition, and paths to bk2 files. I would advise again just globbing through the bk2s and hoping for the best, it's better to rely on a standardized data format that are the event files. Unless I am missing something here?
Currently the repetition ID is based on the number of times a level has been completed in a run, but it doesn't give information about when in the run this repetition was played. It might be more informative to use the absolute order within the run instead.
That would require changes to :
If we agree I can proceed with these changes.
The text was updated successfully, but these errors were encountered: