/version output
This server is running Paper version 26.1.2-74-ver/26.1.2@e4e17fc (2026-07-06T16:51:09Z) (Implementing API version 26.1.2.build.74-stable)
/version Citizens output
Citizens version 2.0.43-SNAPSHOT (build 4226)
Log file
https://paste.denizenscript.com/View/141054
config.yml
https://paste.denizenscript.com/View/141055
saves.yml
https://paste.denizenscript.com/View/141056
Profiler report
No response
Description
In regards to issue #3323, it still persists in the latest build (4226). The posted 'saves.yml' above is the original, which as stated before, had the waypoints manually sorted by myself in a text editor. The below 'saves.yml' is how the initial saves modified the data that was loaded just after server restart:
https://paste.denizenscript.com/View/141058
As you can see, the waypoints for the last two listed NPCs has been shuffled; however, the actual data of the waypoints themselves is correct. The next 'saves.yml' posted below is how the data is further modified by a subsequent '/citizens reload' followed by a '/citizens save':
https://paste.denizenscript.com/View/141059
With this save, you can see that the waypoints have the same ordering by numerical ID as the first save (141058), but the actual waypoint data itself is now corrupted. By comparing the data, you can see that what is shown as waypoint ID '11' in the first save, is now ID '0' in the second save. This shuffling continues with every load/save cycle. It seems that when loading, it disregards the numerical IDs of the waypoints and simply assumes they are listed in ascending order. As to why you couldn't reproduce this previously, I'm not sure, but it certainly impacts my setup.
/versionoutput/version CitizensoutputLog file
https://paste.denizenscript.com/View/141054
config.yml
https://paste.denizenscript.com/View/141055
saves.yml
https://paste.denizenscript.com/View/141056
Profiler report
No response
Description
In regards to issue #3323, it still persists in the latest build (4226). The posted 'saves.yml' above is the original, which as stated before, had the waypoints manually sorted by myself in a text editor. The below 'saves.yml' is how the initial saves modified the data that was loaded just after server restart:
https://paste.denizenscript.com/View/141058
As you can see, the waypoints for the last two listed NPCs has been shuffled; however, the actual data of the waypoints themselves is correct. The next 'saves.yml' posted below is how the data is further modified by a subsequent '/citizens reload' followed by a '/citizens save':
https://paste.denizenscript.com/View/141059
With this save, you can see that the waypoints have the same ordering by numerical ID as the first save (141058), but the actual waypoint data itself is now corrupted. By comparing the data, you can see that what is shown as waypoint ID '11' in the first save, is now ID '0' in the second save. This shuffling continues with every load/save cycle. It seems that when loading, it disregards the numerical IDs of the waypoints and simply assumes they are listed in ascending order. As to why you couldn't reproduce this previously, I'm not sure, but it certainly impacts my setup.