[+][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.

[namida]

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

Maybe a dedicated folder (or subfolder of the replay dir) for these ones, and one file per level (perhaps tracked by level ID)?

[Guigui]

I think namida's suggestion would mean there is a replay file saved somewhere for each level created with the editor.

Actually I do not think this is necessary. The main idea was to have the replay loaded when one quits playtesting a level, makes some changes in the editor, and then comes back playtesting the level again.

This is just to spare the time of playing the level again and again when spending a long time creating it. But I see no need to have a replay autoloaded when I edit a level I worked on some days/months/years ago.

So yes, I think a single .nxrp file which vanishes whenever I close the editor or load another level is enough for my needs ; that is unless another level designer thinks otherwise.

[WillLem]

I can see the merits of both ideas tbh.

A single replay keeps the feature neat, and focuses it on the level currently being worked on.

Multiple replays (one per level) does mean that a 'solution replay' is essentially being generated and stored per-level. This can be used to track later backroute fixes, and will no doubt come in handy if the author has forgotten the solution to their own level (I have done this a number of times!)

It could be confusing for a player to playtest a level and see that a replay has been loaded, though.

Feedback welcome.

[WillLem]

Question: should the replay only be saved (and loaded) if it successfully completes the level, or should it be saved (and loaded) regardless?

[Guigui]

I think save and load replay in any case. The main aim is to not have to replay the level up to the point where modifications have been made, so no problem if previous play was not a solve.

As for keeping a single replay or a full set, I still think a single would be enough.
If I want to make a solution folder, I can make the effort to click the 'save replay' button, and store the replays where I want to keep them.

[WillLem]

I think save and load replay in any case.

Agreed, for the same reason you mentioned.

As for keeping a single replay or a full set, I still think a single would be enough.

If a user is working on one level at a time, a single replay is enough. But they might be working on several levels in a single session, in which case it may be useful for them to be able to come back to a level they were working on earlier.

One approach might be to save as many replays as necessary (keeping to a maximum of one per level), and clear them all when the Editor is closed. This could also be made optional (i.e. Keep / Delete), so that users can choose whatever best fits their workflow.

[Guigui]

Oh yes, clear the replays only when the editor is closed looks like the best option.

Also giving the option to choose whether to keep or delete works for flexibility and user comfort.