It seems the API server was not well prepared for the re-ordering of the levels. The tapes are correct according to the final level order and I can replay them in R'n'D, but the names shown on the web interface are the "old" names, before the re-ordering:
Oops, indeed.
The reason for this is that the first time a score (and score tape) is submitted for a certain level and level set, a database record for this level and level set are created on the high score server, using the submitted level name and level set name (as the high score server may not have this information available at this time). If the level or level set is renamed later, this does not change the level or level set name on the server anymore. :-/
So I guess the highscore server identifies level sets by their full name as given in the levelinfo.conf file, is this correct?
Yes, that's correct. In fact, the level set is determined by first checking the level set identifier (which is the name of the sub-directory of the level set, which was "bugmine" for your level set, which matched for your own test levels, but did not match later when you released your level set using the level set identifier (sub-directory name) "nb_bugmine"), and if this does not match, by checking the level set name that is configured in the "levelinfo.conf" file in the "name:" field.
The reason for this is that I found out very early that quite some people rename their unpacked level sets when adding them to the game, therefore changing the "level set identifier" to something different, but usually do not edit the file "levelinfo.conf" (or do only one of the above changes, but not both). So I also check the "verbose name" of the level set to try a successful match (instead of recognizing that level set as a new one, which would result in scores not shown anywhere else as for the user who submitted that tape).
Because I thought it would use the directory name (like in levelsetup.conf) and actually tried to avoid this kind of trouble by doing the re-ordering to a new directory with a slightly different name, but both were using "Niko's Bug Mine" in the levelinfo.conf

That was principally a very good idea, but the high score server could not be tricked that easily...
To do some testing on the high score server with a new level set still in development and testing before finally releasing it, you could do any of the following:
1. Use the high score server that is used for testing instead of the "real" high score server (maybe with a second, dedicated user just for this purpose, so only have to switch R'n'D users, and do not have to edit files when switching from "test mode" to "normal mode" and vice versa).
To do this, just edit the file "serversetup.conf" (or "users/00x/serversetup.conf" for a separate user with the number "00x") inside the R'n'D personal data directory, and just change the entry
Code: Select all
api_server_hostname: api.artsoft.org
to
Code: Select all
api_server_hostname: api-test.artsoft.org
That's all!
Or, 2. Use a different level set sub-directory name ("level set identifier")
and a different level set name from what you plan to use for the final release of the new level set. This way, the high score server cannot find out anymore that a given score is related to this level set!
For example, for the second "Bug Mine" set, you could just use something like "test_bugmine_2" for the level set folder name, and "Niko's Bug Mine 2 (Test)" for the level set name (and remove the "test" addition for the release). That should work as expected.