V11.0.0

Fixes

• #529 #824: the manual puzzle reset is more dependable:

  • the confirmation is asked immediately on the first click and waits 10 seconds for the second, so a prompt can no longer land after the reset it was meant to announce, and spamming the button neither resets twice nor leaves a stray window armed;
  • you stay in spectator for a short pause (2 seconds, area_reset_spectator_ticks) so the puzzle's own reset contraptions — levers, command blocks, pistons wired to fire when the area empties — actually run. You are held in place for it, since a spectator flies through walls; looking around still works;
  • a puzzle can no longer be reset over and over in a few seconds, and repeating the request while a vote is running no longer re-announces the counter to everyone in the puzzle.

• #529 #824: checkpoints are now validated the same way wherever they come from. One placed outside its area is really refused instead of being kept after the warning, and one placed by a companion plugin obeys the rules an editor's does: ignored when the server has the checkpoint system switched off, refused inside an emancipation grid that affects players — which would respawn them into it endlessly.

• #529: pasting a schematic, copying a level and generating a race now announce each area they are about to create, so another plugin can refuse it — checked before a single block is placed. No visible change unless a plugin objects.

• #529: switching to spectator inside a puzzle, then leaving edition mode and walking out, no longer empties your inventory. Your items are put back where they belong instead of being restored too early and then lost.

• #529: teleporting to an area by its id now really requires the admin permission — until now the refusal was shown and the teleport happened anyway. The "no permission" notice is also no longer sent twice.

• #529: deleting a puzzle now closes the menus other editors had open on it. Until now they kept a menu pointing at an area that no longer existed, because the deleted area was looked for after it had already gone.

• #529: being in edition mode no longer stands in for the edit permission. Until now, opening the editor granted the right to keep editing even if the permission was later lost, and it was only dropped on disconnect — so someone could keep editing anywhere for the rest of their session. The permission is now checked on every action. Nothing changes for an editor who holds it, since opening the editor required it in the first place.

• #529: asking for the info item or a race exit-teleporter wand you already have no longer hands you another one. Both items pile up otherwise, since nothing ever takes them back — the info item was only looked for in your hotbar, and the wand was not looked for at all.

• #529: players can only teleport into a race that is finished — a race still being built no longer accepts visitors and no longer shows up in the command's suggestions. Admins are unaffected: they keep access to every runnable race, suggestions included, so they can still walk a race they are testing. Asking for a race's results now only suggests races that have actually been run, whatever their state.

Technical changes

• #529: For plugin developers — new ways in. A companion plugin can now mark areas as solved for a player without them playing, and take a set back (granted wins count in the statistics but never carry a time, a record or a "first run", so no ranking is disturbed); tell an editor's action from a player's move on the rotate and sphere-resize events, so restricting editing no longer means blocking play; follow a player into an area whatever their game mode with PlayerEnteredAreaBoundsEvent, where PlayerEnteredAreaEvent keeps meaning "started playing this puzzle"; and veto an elevator snapshot refresh, an area merge or a resize, per player. No visible change unless a plugin uses them.

• #529: the public server pack still ships without any of the server's Discord webhooks, but the beta mirror now keeps the two that testing depends on — /puzzle suggest and /puzzle report — so feedback raised while rehearsing a release reaches the same channels as a player's. No in-game effect, and nothing new in the downloadable pack.

• #529: Permission change. Creating an area, merging two areas, deleting cubes or portals in bulk, and force-activating an area now require the admin permission instead of the edit permission. These act on coordinates or ids rather than on where you stand, so they were the ones a puzzle editor could use far outside the puzzle they were working on. Force-activation already refused non-admins — only its advertised permission was wrong. Editors keep everything that acts on the puzzle they are standing in.

• #529: For plugin developers — rebuild required. AreaResizedEvent gives way to AreaBoundsChangedEvent, which announces every change of an area's shape, the merge growth included (silent until now), and carries the area id rather than the area itself: resolve it by id or by the old corners, never with a lookup that loads it. PlayerPermissionsCheckEvent is removed — it never carried the result it was given, and was never fired at all on the check nearly every command uses — and Permission.hasPermission(Player) is replaced by the identical hasPermission(CommandSender). The two mirror events now inherit their permission-bypass flag from the shared base class, so a listener registered on that class finally receives them. Existing calls compile unchanged; a plugin built against an older release must be rebuilt. No in-game effect.