lasersenigma

V8.29.2

Features

• #711: a new /lasersenigma area merge <id1> <id2> confirm command combines two areas into one — the first area keeps its settings and grows to cover both, while the second is absorbed and removed. The confirm keyword is always required to avoid accidents, the merge is refused if the two areas are more than 300 blocks apart or if a third area sits between them, and both areas must be empty when you run it. Records and progress on the merged areas are reset.
• #745: you can now reset a puzzle on demand, without leaving the area. Use the new /lasersenigma area reset command or the reset item handed to you when you enter a puzzle (a second click within a short delay, or a confirmation prompt, avoids accidental resets). The puzzle returns to its initial state and you are sent back to the area checkpoint. When several players share a puzzle, the reset only happens once everyone has agreed. The reset item is locked in place (it cannot be moved, dropped or lost), and server admins can change its hotbar slot or turn it off entirely in the config.
• #752: a new /lasersenigma cube delete command lets you remove cubes dispensed by Cube Distributors — by single block (location), by region (cuboid), or the ones held in hand by players (player), with an optional standard/concentrator type filter. Cubes resting on the ground, carried by a player or still falling are all removed.

Fixes

• #728: the "time since activation" condition now works for both components and area victory conditions — the elapsed time used to stay stuck at 0 (so the condition never triggered) when the area was first entered in creative or edit mode. The timer now starts as soon as the area becomes active.
• #727: conditional blocks (redstone / appearing / disappearing) now behave correctly when a condition duration is set around a room that empties. A block configured to fire "when the last player leaves" (Players mod, min 0 / max 0) now triggers reliably the instant the room empties — a duration of 2 ticks or more used to silently prevent it from ever triggering — and its "Durations" button now explains that durations have no effect on that configuration. A presence-detecting block no longer risks staying stuck on after everyone has left, and the "minimum state hold" duration is now counted in real time regardless of how many areas are active.

Technical changes

• #732: the plugin's layered architecture (Command/Inventory/Listener/Task → Controller → Service → Manager/Repository → Mapper → Entity) is now guarded by automated ArchUnit tests that run on every build. Internal change only — no visible effect in-game.