This one seems very similar to this idea, which seemed to have a good amount of support from multiple users. Namida also seemed to think that the codebase would support it in all but auto-scrolling the screen according to the user's mouse movements.

As of 2.7, SuperLemmix now has .nxrp file association - i.e. if you right-click a .nxrp file in Windows and associate it with SuperLemmix.exe, then double click the .nxrp, it will open SuperLemmix and auto-load both the level and the replay (albeit to Preview screen rather than opening the level directly - this is so that the user can make sure that the correct level has been loaded). There is also the Mass Replay Checker, which already auto-plays replays, it just doesn't render them.

In theory, we could harness these capabilities to play multiple replay files back-to-back. We'd generate and store a list of replays from a specific directory, and then auto-load each one in turn, always bypassing the Preview/Postview screens (or, perhaps, displaying them for 5 seconds or so between levels).

Not out of the question, and we may even be able to address the issue of screen movement not being saved in the replay - it seems like this would almost be a must for this feature anyway. At the very least, auto-loading replays shouldn't be too difficult even if we can't also record screen movement. We just generate a list, then iterate through the list matching each replay to a level file, load the level, load the replay, move on to the next one. It'd probably be best to skip any cases of "level not found" as well.

With that in mind - as of 2.8, SuperLemmix will have the ability to write a replay's Mass Replay Check result to the filename (I'll see if it's also possible to write the result to the replay file itself), that way we could have the proposed auto-play/"screensaver" feature only play successful replays.

Then, it would be up to the user whether they wanted to load only replays for a specific pack, or for a random selection of levels. The button would open a file browser, and you'd select which folder of replays you wanted to play.

I've added this one to the wish list.

12.13 Exp (Build 4098 | Commit 00a392b)

Giving this a quick bump. The Forums are super busy at the moment, which is great to see! I realise I'm creating a lot of topics myself - nothing new about that, I suppose!

I just want to give people an opportunity to speak up if they have an opinion.

You're not exiting the monster, you're continuing into tests that care for (not success), but not for (not talisman) and overwrite the result that depended on your test for success:

I see what you mean, but this happens in the very next block:

                if Game.GameResultRec.gSuccess then
                begin
                  if Game.GameResultRec.gGotTalisman then

This makes me wonder whether gGotTalisman does indeed imply gSuccess. However, a quick search elsewhere in the codebase doesn't make it clear that these conditions are definitely mutually inclusive.

So, I've committed and pushed your suggested change. You're right, let's not assume anything.

I'll have time for code review tonight, Friday 3rd, 17:00 UTC, or anytime on the weekend.

Weekend is good for me too, shall we aim for 1700 UTC Saturday?

Managed to get this far with it today, pinching myself as this time yesterday I wasn't even sure this was possible:



The icons are also slightly resized so that they appear the same size relative to the object when zooming in; this seems better. The next step is to add individual icons for each skill, and center the icons rather than draw them left-to-right. That's after snooker, sleep and cleaning my car.

Getting somewhere! The little square is a test placeholder, obviously drawn in completely the wrong place, but each anchors to its object when moved around!

This will do in the meantime. In a lightbulb moment I realised that the Editor already has a way of writing text above objects, i.e. the object's index when there is (> 1)!

So, harnessed this to write the skill flags. We can make it optional if people think it would be too distracting: