This will just be a ramble about functionality that I find useful from previous go/css server networks that I played on that I miss in SurfsUp.
General / Surf
- The absence of checkpoints. These are very useful to gauge how you are doing mid-run.
- Pre-strafe info, although this kind of overlaps with the checkpoint thing.
- All of this would be nice to have summarized in a (potentially separate) customizable text window that displays e.g. my prestrafe speed, units on hitting checkpoint, time comparison to WR or a different metric.
- Comparing times (in-run) not just to WR, but e.g. to TOP10 or a specific rank of choice.
The ability to paint. This is super useful for marking where to leave a or enter a ramp.This exists.- Startpos. Startpos allows you to set a custom starting position within the boundaries of the start zone. Prevents huge amounts of walking at times.
Saveloc
- I previously asked why there is a limit of 10 savelocs in #general, and I was asked "why do you need more than 10"? Sometimes on longer maps you will make accidental locs or just try to perfect a certain section and it takes you a bunch. Also, as I imagine much harder / longer maps will be added (all maps in the game at this point are easy) 10 is definitely not future proof. They are not stored persistently nor do I imagine they are large "entities" or memory intensive, but please correct me if I'm wrong. It just feels arbitrary.
- I would like to add that being able to reproduce / share savelocs is also desirable. For example some surf timers print out a string of text that basically encodes the x,y,z velocity and everything needed to recreate the saveloc. This is useful for some who want to reuse a saveloc they made previously. Most surftimers additionally give an ID (that is active within the map rotation) so other players can use a command to load in that saveloc and try it for themselves.
I have more but space is running out so maybe another time 🙂 thx