Implemented Couple suggestions

1.) Web stuff - don't see this happening any time soon.
The site we use atm was slapped together by the original plugin author (and some contributors), and also looks like this.
Best way would be to re-do that entire thing, for which I neither have time nor energy (preparing the store rollout is planned next).
There is, however, some basic sorting available in the "View all records" dropdown on a player's page - https://files.f-o-g.eu/aa925adgfgg4243adbgg4f108c95db1c - you just have to click on "View all records" again after clicking one of the headers.

2.) Will look into adding teleport-to-stage wrcps once I get time, can't promise anything though.
Due to the current design of the plugin, I would have to start the timer when leaving the stage zone and stop it when reaching the end (?) or next stage.
This is required to actually see which time you will get (the timer in the center of the screen).

3.) Don't really understand that one - the plugin already shows your delta to the current WR time on the checkpoint when you pass it.
EDIT: Sey has explained it to me now - the plugin should print the time difference to the entire map wr, not only cp wr as well.
This would only work for new runs, as the old ones will not have the information if the cps were part of a WR.

 

Giving an update on 2.):
The feature is mostly working flawlessly, in a way which doesn't require any extra zone types / rezoning.
It works by starting your timer in a sort-of "unranked" mode after you leave a stage and it isn't running already, thus allowing the WR CP plugin to function as it does now.
Any finishes made (reaching the end zone), will not be counted, as otherwise, you could simply tele to the last stage, surf to the end and get <5 sec times.

So, TL;DR:

• If you do a regular run (leave the start zone and surf until the end), nothing changes, same behaviour as current
• If you teleport to a zone using !s <number>, e.g. !s5 and leave the zone (so leave the platform in most cases), the timer will start again, and you will be able to complete with checkpoint times. Touching the end zone will neither record your time, nor trigger any world records/bot saves.

However, there is still a pretty major problem with time differences.
Basically, the WR CP plugin counts the time between first touching a checkpoint (A) and touching the next one (B), thus counting from the beginning.
Now, the change above caused that the timer will start once you leave the checkpoint zone, so you will start with 00:00 and get much better times.
Due to this, I was able to get placed into the top 10 without much effort.

Graphical illustration for easier understanding:


To fix this problem, the only real viable solution would be to start counting stage times only once you leave the checkpoint zone in regular runs as well.

Example:
start -> reach stage 1 [time: 4.4 seconds] (start touching the zone) -> leave stage 1 zone (and surf the stage) [time: 4.7 seconds] -> reach stage 2 [8.4 seconds] (start touch)
Your time would be: 3.7 seconds for stage 1. With the current system, it would be 4.0 seconds.

Failing/retrying the stage would not reset your stage start time, so leaving the zone of stage 1 multiple times in a row would still count as 3.7 seconds.

Please let me know what you think about this change (and if you understood my explanations), or feel free to suggest a better variant.
I also thought about adding some sort of penalty time when using !s<stage>, but that would be rather arbitary (how much time should be plugin add? 500ms? 750ms?)

 

Updating this again:
the behaviour as described above is now working, only two bugs (discovered from by testing) remain:
- if you use !rs to restart the current stage, a partial run will be started - !back behaves the same as !sX
- sometimes, the timer for partial runs does not start if you teleport between different stages (if you are in the air).

 

Both bugs mentioned above have been fixed now, and the feature is now fully working (imo).
If you want to test it, please contact @Venom to start up the test server and give you the password.

 

Reminding @Seynethic again

 

1.) Prehopping: this should only be disabled when doing a "partial" run? Aka. typing !s 5.
2.) That's mostly because the end zone has its own type and isn't considered a "level" zone itself. Could probably check for it in a forward.
3.) Originally planned it like that (falling down and touching the stage zone again would stop your timer), but ran into some problems with the timer starting again randomly.
Should probably work now, as I have improved the handling of that stuff a lot.

Not sure when to implement/test it though, considering I currently have a 4 week global cooldown (would need to test with an alt..)

 

All 3 points implemented, uploaded a new version on the test server.
While I was at it, also took the opportunity to change the color of the time (in the middle) from green to blue if you are doing a "partial" run.

@Seynethic

 

WR run difference calculation/storing is now implemented as well.
The new version is currently installed on 1-6, if everything works fine, I will install it on the other servers around beginning next week.

Marking as implemented (my stance on the web stuff hasn't changed).
Thanks to @Rizor / @Seynethic / @Avaritia (and everyone else) for helping me test.

 

Marking as implemented, now installed on all our Surf/Bhop servers.