[+][SUG][PL/ED] Keep playtest replay in memory

[WillLem]

From Guigui in this topic.

I'd appreciate if replay carries when using the editor.
To be clearer : create a level, playtest it, exit to editor to make changes, play test the level again and find your previous replay ready for you.

[WillLem]

Good idea.

The question is really how to do this. We can store a temporary replay file in the directory which always keeps the same name, updating the internal data whenever a level is playtested. If we're in Playtest Mode and the replay data matches the level, we load the replay. Otherwise, we only overwrite.

There may be a better way, though. My goal would be to not litter the directory with temporary replays, ideally.

Suggestions welcome.

[Guigui]

Your method of implementations sounds good.

I would add : delete temporary replay file when the editor is closed, or when a new level is loaded within the editor.
This way you always create a single temp replay file which vanishes when you end your work session with the current level.

With this method, you do not have a replay auto-loaded when you start working on another level. But this is not a problem imo, because then you do not have your intended solution (or close) autoloaded when you start working on this level, instead you have a fresh start and this helps tracking backroutes.