v26.2-1.0.0

BlueMap Sign Markers 1.0.0

Changes since v26.2-0.17.1.

New Features

Line, shape, and extrude markers (#7, #8, #196, #197)

A marker group's type is no longer limited to a single point. Signs sharing a group's prefix and the same label (the sign's description line) now become one marker with a shape:

• LINE — an ordered polyline connecting members in placement order. Appears once 2+ signs exist.
• SHAPE — same grouping, rendered as a filled polygon. Appears once 3+ signs exist; height comes from the tallest member.
• EXTRUDE — same grouping, rendered as a solid 3D volume from the lowest member's height to the tallest.

Editing, moving, or removing a member sign updates or removes the marker automatically. Moving a sign between groups — even across types (POI ↔ LINE ↔ SHAPE ↔ EXTRUDE) — leaves no orphaned marker behind.

Player-controlled marker colors (#198)

Opt-in per group via allowPlayerColors. Once enabled, a player can set a LINE/SHAPE/EXTRUDE marker's color by right-clicking one of its member signs with a dye — no config edit needed. The earliest-placed dyed member wins; the marker's alpha still comes from the group's configured color.

Marker polish: sorting, toggleable, depth-test, CSS classes (#197)

Four new passthrough fields for finer control over marker rendering:

• sorting — order a group in the map's layer menu.
• toggleable — force a marker-set to stay visible, un-hideable by players.
• depthTest — keep an underground trail/region visible through terrain (LINE/SHAPE/EXTRUDE only).
• cssClasses — hook POI markers into BlueMap's custom.css.

Per-map marker visibility (#67)

A sign's marker now only renders on a BlueMap map if the sign (or, for LINE/SHAPE/EXTRUDE, at least one member) falls inside that map's own render-mask bounds (config/bluemap/maps/<id>.conf). Fixes markers bleeding onto maps that shouldn't show them (e.g. a nether-roof map showing overworld-only markers).

Stale-prefix self-healing (#190)

Previously, editing a REGEX marker group's prefix could permanently orphan already-placed signs — they'd vanish from the map and never come back without a manual re-edit. Signs now self-heal on /bluemap reload: the mod re-parses each sign's original text against the new config instead of trusting a stale cached match.

Upgrade Notes for Server Admins

⚠️ Back up your world save and config/bluemapsignmarkers/ before upgrading. Standard precaution for any upgrade touching persisted data.

No manual config changes required. Everything below happens automatically on first server start after upgrading:

• Sign data migrates in place (persistence format V4 → V6): adds raw sign text (needed for prefix self-healing) and per-sign dye color (needed for player-controlled colors). Pre-upgrade signs backfill with safe defaults (undyed). Each migrated file is backed up (.v4.bak, .v5.bak) before being overwritten.
• Existing configs behave identically after upgrading — every new MarkerGroup field defaults to today's current behavior (toggleable: true, depthTest: true, sorting: 0, allowPlayerColors: false, empty cssClasses).

Run /bluemap reload once after upgrading if any of your BlueMap maps have a render-mask configured. This sweeps away markers that were already showing on a map outside its render bounds before this fix — a plain server restart alone does not trigger the sweep.

Fabric API dependency changed (#22). The mod now declares a dependency on the fabric-lifecycle-events-v1 module specifically, instead of the whole Fabric API. No action needed if you run a full Fabric API jar (which BlueMap itself already requires).

New Configuration Options

New MarkerGroup fields since v26.2-0.17.1 — full schema/defaults/examples are in README.md's "Marker Groups" section:

Field	Applies to	What it does
type: LINE / SHAPE / EXTRUDE	group type	New marker shapes beyond POI — see Features above
lineWidth	LINE/SHAPE/EXTRUDE	Border width in pixels
lineColor	LINE/SHAPE/EXTRUDE	Border hex color (with alpha)
fillColor	SHAPE/EXTRUDE	Interior hex color (with alpha)
allowPlayerColors	LINE/SHAPE/EXTRUDE	Let players set marker color by dyeing a member sign
sorting	all types	Marker-set order in the map's layer menu
toggleable	all types	Whether players can hide the marker-set at all
depthTest	LINE/SHAPE/EXTRUDE	Whether terrain occludes the marker
cssClasses	POI	CSS classes for custom.css styling

Setting a field on a group type it doesn't apply to isn't an error — the mod logs a warning and ignores it.