BlockMemory 1.6.8

BlockMemory 1.6.8 focuses on investigation quality-of-life, saved alert history, improved saved area workflows, clearer per-world config guidance, and vertical Y-range support for watched/suppressed areas used by burst alerts.

Added

Saved burst alert history

Added a saved alert history workflow for reviewing and managing recorded burst alerts:

• /blockmemory alerts
• /blockmemory alerts inspect <id>
• /blockmemory alerts delete <id>

Saved alert IDs are now stable and non-reused after deletions, so staff can reliably reference a specific alert later.

Saved area command improvements

Saved area workflows have been expanded with full id-or-name support across the main saved-area flow:

• /blockmemory area watch add <name> <x1> <y1> <z1> <x2> <y2> <z2>
• /blockmemory area suppress add <name> <x1> <y1> <z1> <x2> <y2> <z2>
• /blockmemory area inspect <idOrName>
• /blockmemory area watch remove <idOrName>
• /blockmemory area suppress remove <idOrName>

Saved area name autocomplete was added for inspect/remove flows so watched and suppressed areas are easier to select in chat.

Y-range support for saved areas

Saved watched/suppressed areas now support vertical bounds using minY and maxY.

This means burst alert matching can now work properly for elevated builds, sky structures, underground zones, layered bases, and other vertically separated areas in the same chunk footprint.

Y-aware burst alert matching

Burst suppression and watched-area naming can now use Y-level during area matching.

This improves accuracy for servers with builds above or below one another and reduces the chance of area rules applying too broadly across the full world height.

Y-aware config formats

Config-defined watched/suppressed burst alert areas were expanded to support vertical range fields as well.

Block Scanner assessment copy action

Added a [COPY] clipboard action to Block Scanner assessment output.

This copies a compact scan summary including radius, tracked block counts, entity counts, assessment, and confidence while keeping existing TXT/JSON export behavior unchanged.

Investigation tool subtitle lines

Added small descriptive subtitle lines to the investigation tools:

• Block Scanner — Inspects tracked block history
• Presence Wand — Shows contextual player presence

Generated world readme

BlockMemory now auto-generates a blockmemory-readme.txt file inside each world’s serverconfig folder if missing.

This readme explains:

• that active BlockMemory server config is stored per-world
• where blockmemory-server.toml is located
• what major BlockMemory systems do
• how burst alert tuning works
• config-defined watched/suppressed area formats
• the difference between config areas and saved in-game areas
• what is generated world data versus what is user-edited config

The file is created if missing and is not overwritten if it already exists.

Changed

Block Scanner workflow cleanup

Removed legacy /blockmemory toggle and the old enabled-state gate tied to Block Scanner use.

Block Scanner now uses the current staff-only workflow based on permission + held item check only.

Saved area UX improvements

Improved saved area inspection and removal UX with:

• id-or-name lookup
• exact-name support
• autocomplete suggestions
• updated help text
• vertical bounds reflected in saved-area inspection output

Incident inspect color consistency

Incident inspect view now uses the same review-state color mapping as the incidents list:

• UNREVIEWED — red
• REVIEWED — green
• FALSE_POSITIVE — dark gray
• ACTION_TAKEN — gold

Block Scanner UUID polish

Improved Block Scanner UUID presentation and safety:

• UUID click action now copies directly to clipboard
• hover text matches the copy behavior
• player-name lookup is null-safe when placement UUID is missing
• standardized Unknown / UNKNOWN wording for consistency
• Internal polish
• Removed redundant removal-field reassignment in BlockMemoryData.put(...)
• Improved generated readme clarity and structure
• Improved help text to reflect current command behavior
• Improved area-related documentation to reflect Y-aware formats

Notes

Per-world config location

Active BlockMemory server config is stored per world in that world’s serverconfig folder.

Why Y-range support matters

Saved watched/suppressed areas and burst alert matching can now distinguish between builds sharing the same X/Z chunk footprint but existing at different heights.

This is especially useful for servers with stacked builds, sky builds, underground bases, floating structures, and multi-level protected areas.

As always, feedback and suggestions are very welcome!