You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our server has ~9,300 shape markers in one marker set (land claims, simple rectangles). live/markers.json is ~5.4 MB.
Open the map in flat view.
Drag the map around and zoom in and out over an area with claims.
Expected result
The map stays smooth, the same as without the marker set.
Actual result
The whole map feels sluggish. Measured on a fast machine (Apple M1 Max, Chromium, 1600×1000 @2x) with the latest master:
FPS
Doing nothing, overview with claims on screen
26
Dragging the map
25
Dragging while fully zoomed out
16
Zooming in and out
23
With the marker set removed, or with shape markers drawn in batches (see below), the same scenarios run at 58–60 FPS. Weaker laptops and phones are hit much harder.
We made a patch that draws all shape markers of a set with one mesh per style. Happy to open a PR if you are interested.
Known issue, bluemap's marker system was never designed to hold more than ~1000 markers ..
I am already working on a full webapp rewrite in the background, which is planned to also get a better system for markers, which will hopefully fix this issue as well. Don't expect a "quick fix" for this though.
@strobil One suggestion: Do you actually have 9300 claims? Because if your plugin currently just marks e.g. every claimed chunk with a separate marker then that is incredibly inefficient. Instead, you should try to merge chunks that are next to each other into one shape-marker. That way you can reduce markers many times. Here is a library that helps you convert many chunks into outline-shapes :)
If you need help with this, please visit our discord!
Thanks! They are real claims, not chunks: one ProtectionStones region per marker, ~3900 different owners. Each region is a separate unit with its own owners, members and flags, so players need to see every one with its actual borders; merging them would hide who can build where. Even merging only touching regions of the same owner gets us from 9334 to just 6444.
Activity
TBlueF commentedon Nov 7, 2026
Known issue, bluemap's marker system was never designed to hold more than ~1000 markers ..
I am already working on a full webapp rewrite in the background, which is planned to also get a better system for markers, which will hopefully fix this issue as well. Don't expect a "quick fix" for this though.
TBlueF commentedon Nov 7, 2026
@strobil One suggestion: Do you actually have 9300 claims? Because if your plugin currently just marks e.g. every claimed chunk with a separate marker then that is incredibly inefficient. Instead, you should try to merge chunks that are next to each other into one shape-marker. That way you can reduce markers many times. Here is a library that helps you convert many chunks into outline-shapes :)
If you need help with this, please visit our discord!
strobil commentedon Nov 7, 2026
Thanks! They are real claims, not chunks: one ProtectionStones region per marker, ~3900 different owners. Each region is a separate unit with its own owners, members and flags, so players need to see every one with its actual borders; merging them would hide who can build where. Even merging only touching regions of the same owner gets us from 9334 to just 6444.
TBlueF commentedon Nov 7, 2026
Yeah then i have no immediate solution for you unfortunately, i am working on a better webapp already, but it will still take a while
strobil commentedon Nov 7, 2026
Thanks a lot for the quick replies and for all the great work on BlueMap, our players love it! Looking forward to the new webapp.