Broken Global waystones remain on network and bluemap

[NoYavy]

Minecraft Version

1.21.1 (LTS)

Mod Loader

NeoForge

Describe the Issue

Hi, I replied on #669 but since it's closed for three years and not for the version where I encountered this, I figured I'd open a new issue.
Since then I figured out that you can remove the waystones in the gui by holding shift and clicking the cross, but the marker on bluemap remains

Hey I have this issue on 1.21.1 with mod version 21.1.27, is there a command or something to just delete them (they are both in the gui and on bluemap there are markers but no block anymore)

Logs

I sadly do not have the logs from the moment this happened anymore.
The only lines mentioning waystones right now are:

[04Mar2026 22:04:38.879] [main/INFO] [net.neoforged.fml.loading.moddiscovery.ModDiscoverer/SCAN]: Found mod file "waystones-neoforge-1.21.1-21.1.28.jar" [locator: {mods folder locator at /srv/minecraft/mods}, reader: mod manifest]
[04Mar2026 22:04:46.929] [main/WARN] [mixin/]: Reference map 'waystones.refmap.json' for waystones.mixins.json could not be read. If this is a development environment you can ignore this message
[04Mar2026 22:04:59.103] [modloading-worker-0/INFO] [net.blay09.mods.balm.neoforge.config.NeoForgeBalmConfig/]: Registering config for waystones:common (COMMON) with 34 properties.
[04Mar2026 22:05:09.159] [modloading-worker-0/INFO] [snownee.jade.Jade/]: Start loading plugin from net.blay09.mods.waystones.compat.JadeIntegration

[BlayTheNinth]

You can hold shift while in creative mode to delete a global waystone.

[NoYavy]

Yeah that's what I did, and in the gui it is gone but as you can see the markers are still there:

Since then I figured out that you can remove the waystones in the gui by holding shift and clicking the cross, but the marker on bluemap remains

And now there is nothing I can shift click to remove them, since the waystones do not show up anymore

[BlayTheNinth]

BlueMap markers managed by Waystones are freshly regenerated whenever the server restarts. If markers remain despite a restart, they're probably not within the waystones:waystones marker set anymore and would have to be removed manually within BlueMap.

If they are inside the Waystones marker set, it could be that there's still an entry for the waystones in your waystones database (which happens for silk-touched waystones so they don't lose their data). I will update the BlueMap integration to ignore transient-marked waystones.