VanishCore

[1.0.5] - 2026-07-02

Fixed

• Silent chest: double chests were still visibly opening for viewers. Minecraft sends a BLOCK_ACTION lid-animation packet for both halves of a double chest when either half is opened, but SilentChestManager only tracked the block that was actually right-clicked, so the untracked half's animation packet went through unsuppressed. Now the paired half is detected via BlockData (Chest.Type/Chest.getFacing()) and tracked alongside the clicked block. Found by adding a protocollib.debug config flag that logs every packet the filter inspects plus whether it matched — confirmed ProtocolLib 5.5.0-SNAPSHOT-5a9afed packet field reads (BLOCK_ACTION position, NAMED_SOUND_EFFECT fixed-point position) are all correct on MC 26.1.2 despite ProtocolLib's own "not yet tested" warning for that version; the miss was purely the double-chest tracking gap.
• Silent chest didn't work at all for barrels: barrels don't use the chest-style BLOCK_ACTION lid-animation packet — their open/closed lid is an actual block-state property, sent to the client as a plain block-state-update packet (BLOCK_CHANGE), which SilentChestManager never listened to. Added BLOCK_CHANGE to the packet filter alongside BLOCK_ACTION/NAMED_SOUND_EFFECT, suppressed the same way when it lands on a tracked container coordinate.
• Silent chest didn't work at all for copper chests: COPPER_CHEST, EXPOSED_COPPER_CHEST, WEATHERED_COPPER_CHEST, OXIDIZED_COPPER_CHEST, and their four waxed variants exist as real Materials on this Paper 1.21.11 build but were simply missing from CONTAINER_MATERIALS, so they were never tracked as opened at all. Added all 8. They share org.bukkit.block.data.type.Chest with regular chests, so double-chest pairing covers them automatically — no extra logic needed there.
• Silent chest still leaked intermittently after the double-chest fix. Root cause: recentOpens was only ever populated from PlayerInteractEvent (RIGHT_CLICK_BLOCK), so any container opened through a path that doesn't fire that exact event/action (another plugin forcing the inventory open, edge cases in event ordering, etc.) never got tracked — its BLOCK_ACTION/NAMED_SOUND_EFFECT packets sailed through unsuppressed. Added InventoryOpenEvent as a second, independent tracking path: it fires whenever a container inventory is actually opened for a player regardless of how, so it catches whatever the interact handler misses. Extracted the shared "track this block (+ its double-chest partner)" logic into trackContainerOpen(), used by both handlers plus the existing close handler.

Added

• A silent-chest confirmation message for the vanished player themselves — messages.silent-chest-open (default "&8[&5Vanish&8] &7Opened silently — no one saw or heard it."), sent once per confirmed open (from the InventoryOpenEvent handler, not the interact-event safety net, so double chests and the redundant tracking path don't double-send it). Toggle with protocollib.notify-silent-chest-open (default true).
• protocollib.debug config key (default false) — logs every BLOCK_ACTION/NAMED_SOUND_EFFECT packet the silent-chest filter inspects, whether it matched a tracked open, and any packet-read exceptions. Diagnostic aid, noisy in normal play.
• /vanish reload (/v reload, permission vanishcore.reload) — reloads config.yml without a restart. Works from console too. Re-reads protocollib.debug and the Bedrock skip flag on SilentChestManager live; most other config reads (messages, permission checks) were already dynamic. Note: toggling protocollib.silent-chest-open from disabled to enabled still requires a restart, since the packet listener is only registered once at startup.