Related issue:
NL shows "solved" tick if I download a replay and watch itThe main problem here is that (contrary to Lix), NeoLemmix has no player-name. So unless we add this, we have no way to correctly detect the author of the replay file.
And regarding namida's suggestions, there are some problems:
1) What if a player switches computers (or just the NeoLemmix folder) and runs their own replays (possibly through the mass replay checker)? Then they would want to keep their records. Yes, they could as well copy the userdata file, but when I do a clean-up and set up a new NeoLemmix instance, then I regularly forget doing that.
2) More importantly: What if a player loads one of their own replays in an attept to optimize it, lets it run for most of the level, then spots a way to improve it, aborts the replay and solves the level? So just using loading a replay at the beginning should not abort updating the trophies. Similarly checking at the end of the level whether we do a replay or not, won't work either. The main problem here is that we can no longer distinguish between having loaded an external replay and consistently replaying it, or replaying the current attempt due to a backwards frameskip. And maybe there is as well the problem of the "action insertion during replay" feature...
By the way: Checking whether a replay is active during the very last frame won't help either, because the player could abort the level after a backwards frameskip.
Upshot is: As far as I can see at the moment, we would need a proper user management to implement this in a sensible way. But I feel that there are more important things to add at the moment.
Current workaround, if you still have your own records in the way of a replay: After playing an external replay, go to the userdata.nxsv file, grep there for the level title (in uppercase with spaces replaced by underscores) and delete the corresponding section between the two dollar signs. Then run your own replay again.