Structural Safety 2.0.0

New Protection System

• Added server-side Adventure-style protection without changing the player’s actual game mode.
• Players remain in Survival while protected-area restrictions are applied automatically.
• Allowed blocks use normal Vanilla mining progress, tools, durability, enchantments, drops and events.
• Added protection for world-generation features in addition to structures.
• Vanilla monster rooms can now be detected and protected.
• Added persistent per-dimension storage for detected feature regions and temporary blocks.

Structure and Feature Rules

• Added individual break rules for every structure and feature.
• Added four rule modes:
  • inherit – use the shared block list
  • extend – shared list plus additional blocks
  • replace – use only the area-specific list
  • none – allow no block breaking
• Rules can be managed through commands or the visual menu.
• Added feature protection, bounds and rescan commands.
• Added throttled scans for already-loaded chunks without generating or loading additional chunks.

Player Information

• /structuralsafety info now detects the structure or feature the player is currently inside.
• Players can see the active area name, ID, break-rule mode and exactly which blocks they may break.
• The command also explains whether sneaking is required and which shared interaction and placement rules apply.
• Added an optional chat hint when entering a protected area.
• Added a separate setting to disable the /structuralsafety info entry hint.
• Added configurable entry, exit and denied-action messages.
• Added configurable protection sounds, escape hints and temporary-block timer feedback.

Server-Side Menu

• Added /structuralsafety menu, using a Vanilla chest interface.
• The menu remains completely server-side and requires no client mod.
• Added visual management for structures, features, break rules, feedback settings and administration tools.
• Added full support for singleplayer through Minecraft’s integrated server.
• Singleplayer world owners can configure the mod even when cheats are disabled.

Administration and Diagnostics

• Added /structuralsafety inspect for live protection, breaking, interaction and placement decisions.
• Added /structuralsafety preview to display protection boundaries using Vanilla particles.
• Added live diagnostics for protection lookups, allowed and denied actions, scans, temporary blocks, audit status and configuration health.
• Added asynchronous rotating audit logs.
• Added safe configuration reloads with validation, rollback and rejected-config backups.
• Added a conservative configuration repair tool.
• Added Vanilla-friendly, anti-grief, strict and adventure-map presets.
• Added fine-grained permissions for viewing, management, inspection, testing, diagnostics, auditing and escaping.
• Added a safer /structuralsafety escape command for players trapped inside protected areas.

Technical Test Mode

• Added a configurable technical test mode.
• Enabled by default in IntelliJ development runs and disabled in packaged releases.
• Added a non-destructive startup self-test.
• Added temporary in-memory structure and feature test areas.
• Added a guided technical test scenario through commands and the server-side menu.
• Test areas use the same protection, mining, placement, feedback and escape systems as real protected areas.

🏜️ Structural Safety — Desert Temple & Trap Update

✨ New

• The Desert Temple's hidden treasure pit is now protected. Until now, protection only covered the temple's main bounding box — the buried chamber with the TNT trap and 4 chests sits ~14 blocks below it and was left completely unprotected, so players could tunnel in and loot or grief it from underneath. Protection now reaches down to cover the secret chamber too.
• Vanilla traps stay active — and still destroy. Protecting a structure must never defuse its traps. The Desert Temple's TNT trap now detonates and breaks blocks exactly like vanilla, even though the area is protected. This works for any protected structure that has a TNT trap, not just the desert temple. Trap damage to players was never affected.
• Non-explosive traps keep working too. Jungle Temple arrow dispensers, tripwires and pressure plates were never blocked — they trigger through redstone/collision, which the mod doesn't touch.

⚙️ Config & Commands

• New config: deep_structures — maps a structure to how many blocks its protection extends below its bounding box. Default: minecraft:desert_pyramid → 15. New admin commands:

  /structuralsafety admin structure deep list
  /structuralsafety admin structure deep add <id>
  /structuralsafety admin structure deep remove <id>

• New toggle: traps_active (default ON) — controls whether vanilla TNT traps may detonate inside protected structures. Available as a clickable status in /structuralsafety admin protection, alongside explosion/fire/lava.
• /structuralsafety info now also shows the number of deep structures and the traps-active status.

🔒 Anti-Grief

These changes don't open any new griefing vectors:

• Players are held in Adventure mode inside protected structures, so they can't place their own TNT there — only the worldgen trap TNT exists inside.
• TNT ignited outside a protected area (e.g. next to a structure) is still blocked from destroying protected blocks.

🔧 Notes

• Existing configs migrate automatically on first launch — your current settings are left untouched.
• Activation is still required. A structure must be enabled (/structuralsafety admin structure protect <id>) for any of this to apply.
• The extended area is a column under the structure footprint, so caves directly beneath the temple are covered too — intended, to stop the trap being bypassed from below.

Structural Safety 1.2.3

New: Environment Protection

Protected structures can now be shielded from environmental block damage — each type can be toggled individually:

• Explosions — TNT, creepers & co. no longer blow holes into protected structures.
• Fire — fire can no longer ignite or burn down blocks inside protected structures (also covers lava-lit fire).
• Lava — flowing lava is kept out of protected structures.

All three are enabled by default, so existing worlds stay protected out of the box. Toggle them via the new clickable panel: /structuralsafety admin protection → click a status to switch it on/off (also works from console/RCON as plain text).

Fixed a subtle gap where fire could still consume flammable blocks (wood) at the edge of a structure even though new fire blocks were being removed. Burning is now blocked on the spread path as well.

Reworked Command Menu

The whole command tree was rebuilt around clear names and clickable menus:

• /structuralsafety — opens the main menu (clickable)
• /structuralsafety info — current settings (now also shows the protection states)
• /structuralsafety escape — teleport to safety
• /structuralsafety admin — admin menu (permission level 2)
  • protection [explosions|fire|lava] [on/off]
  • structure list | protect | unprotect | protectall | unprotectall
  • structure sprawling list | add | remove
  • allow break | interact | place temp | place perm (list/add/remove)
  • time escape <min> | temp <min>
  • opbypass [on/off]

Renamed commands

Compatibility

• Existing config files are migrated automatically; missing keys fall back to the safe default (protection on).
• No world data changes required.

Structural Safety 1.2.3

New: Environment Protection

Protected structures can now be shielded from environmental block damage — each type can be toggled individually:

• Explosions — TNT, creepers & co. no longer blow holes into protected structures.
• Fire — fire can no longer ignite or burn down blocks inside protected structures (also covers lava-lit fire).
• Lava — flowing lava is kept out of protected structures.

All three are enabled by default, so existing worlds stay protected out of the box. Toggle them via the new clickable panel: /structuralsafety admin protection → click a status to switch it on/off (also works from console/RCON as plain text).

Fixed a subtle gap where fire could still consume flammable blocks (wood) at the edge of a structure even though new fire blocks were being removed. Burning is now blocked on the spread path as well.

Reworked Command Menu

The whole command tree was rebuilt around clear names and clickable menus:

• /structuralsafety — opens the main menu (clickable)
• /structuralsafety info — current settings (now also shows the protection states)
• /structuralsafety escape — teleport to safety
• /structuralsafety admin — admin menu (permission level 2)
  • protection [explosions|fire|lava] [on/off]
  • structure list | protect | unprotect | protectall | unprotectall
  • structure sprawling list | add | remove
  • allow break | interact | place temp | place perm (list/add/remove)
  • time escape <min> | temp <min>
  • opbypass [on/off]

Renamed commands

Compatibility

• Existing config files are migrated automatically; missing keys fall back to the safe default (protection on).
• No world data changes required.

Structural Safety 1.2.3

New: Environment Protection

Protected structures can now be shielded from environmental block damage — each type can be toggled individually:

• Explosions — TNT, creepers & co. no longer blow holes into protected structures.
• Fire — fire can no longer ignite or burn down blocks inside protected structures (also covers lava-lit fire).
• Lava — flowing lava is kept out of protected structures.

All three are enabled by default, so existing worlds stay protected out of the box. Toggle them via the new clickable panel: /structuralsafety admin protection → click a status to switch it on/off (also works from console/RCON as plain text).

Fixed a subtle gap where fire could still consume flammable blocks (wood) at the edge of a structure even though new fire blocks were being removed. Burning is now blocked on the spread path as well.

Reworked Command Menu

The whole command tree was rebuilt around clear names and clickable menus:

• /structuralsafety — opens the main menu (clickable)
• /structuralsafety info — current settings (now also shows the protection states)
• /structuralsafety escape — teleport to safety
• /structuralsafety admin — admin menu (permission level 2)
  • protection [explosions|fire|lava] [on/off]
  • structure list | protect | unprotect | protectall | unprotectall
  • structure sprawling list | add | remove
  • allow break | interact | place temp | place perm (list/add/remove)
  • time escape <min> | temp <min>
  • opbypass [on/off]

Renamed commands

Compatibility

• Existing config files are migrated automatically; missing keys fall back to the safe default (protection on).
• No world data changes required.

Structural Safety - 1.2.2

Villages are now fully protected — not just the center. Previously, protection only kicked in inside the tight bounding boxes of individual jigsaw pieces (the well, single houses). The squares, gardens and paths between buildings were left unprotected. From now on, sprawling (loosely-built) structures use the overall bounding box of the StructureStart, so the entire village area is covered

New config list: sprawling_structures Structures on this list use the wide-area protection check. By default, all 5 vanilla village variants are included:

• Plains Village
• Desert Village
• Savanna Village
• Snowy Village
• Taiga Village

New admin commands:

  /structuralsafety admin sprawling list
  /structuralsafety admin sprawling add <id>
  /structuralsafety admin sprawling remove <id>

Tab-completion suggests registered structure IDs — including IDs added by other mods (e.g. ChoiceTheorem's Overhauled Village, Repurposed Structures, …).

/structuralsafety info now displays the number of configured sprawling structures.

🔧 Notes

Activation is still required. Sprawling membership only changes how the protected area is calculated — not whether protection is active. For each structure you still need to run /structuralsafety admin structure add <id> to actually turn protection on.

Existing configs are migrated automatically. On first launch after the update, the 5 vanilla villages are added to sprawling_structures via the existing addIfMissing migration. Your existing settings (structures, items, etc.) are left untouched.

Compact structures are unchanged. Dungeons, mansions, strongholds, fortresses and co. still use the tight per-piece check, so existing balancing for those structures is preserved.

🛠️ Modded Villages (CTOV, Repurposed Structures, …)

Modded village variants are not auto-detected as sprawling, since they live under their own namespaces. Example setup for CTOV:

/structuralsafety admin structure add ctov:plains_giant
/structuralsafety admin sprawling add ctov:plains_giant

You can find available IDs via /structuralsafety admin structure list.

Structural Safety 1.2.1

Changed

• Default behavior: opBypass is now disabled by default. Fresh installs will enforce Adventure Mode inside protected structures even for OP players — singleplayer hosts (automatically OP level 2) now get the protection mechanic out of the box, with no menu toggling or commands required.

Notes

• Existing worlds/configs are untouched: if "op_bypass": true is already set in config/structuralsafety_settings.json, your setting is preserved.
• Admins can toggle the bypass at any time: /structuralsafety admin opbypass <true|false>

Structural Safety 1.2.1

Changed

• Default behavior: opBypass is now disabled by default. Fresh installs will enforce Adventure Mode inside protected structures even for OP players — singleplayer hosts (automatically OP level 2) now get the protection mechanic out of the box, with no menu toggling or commands required.

Notes

• Existing worlds/configs are untouched: if "op_bypass": true is already set in config/structuralsafety_settings.json, your setting is preserved.
• Admins can toggle the bypass at any time: /structuralsafety admin opbypass <true|false>