• Vanish yourself or another online player
• Set an offline player to join vanished
• Local or network wide vanish
• Timed vanish with automatic reappearance and extension
• Explicit on and off commands that cannot accidentally toggle the wrong way
• Silent vanish and reappear options
• Per viewer fake join and quit messages
• Reveal yourself to one viewer without becoming visible to everyone
• Hide from one viewer without changing your global state
• Automatic vanish on join through permissions
• Optional world based profile changes
• Persistent UUID based state across restarts, reloads, and transfers
• Stored actor, cause, profile, scope, reason, case ID, and timestamp

Profiles let staff use different rules for different jobs. Watching a suspected cheater should not need the same setup as building at spawn while hidden.

Included profiles:

• default - a safe general purpose setup
• strict-ghost - no interaction and as little world impact as possible
• observation - detailed monitoring without world changes
• investigation - close observation with stronger audit requirements
• spectator - spectator style movement
• builder - building while hidden
• event-staff - practical event tools with chat protection
• developer - unrestricted testing while invisible
• owner - the highest default visibility level

Layered visibility is optional. When enabled a viewer can see a hidden player only when their see level is high enough for that player's use level.

• Protected accounts
• Per player reveal and hide exceptions
• Separate use and see levels
• Live LuckPerms refresh support
• /vanish whycansee <viewer> <target> for readable visibility explanations

• Player and entity collision prevention
• Hidden hitboxes do not block normal block placement
• Projectiles pass through hidden staff
• Fishing hooks and leads cannot attach to them
• Pressure plates, tripwire, sculk sensors, shriekers, dripleaf, turtle eggs, and farmland protection
• Existing mob targets are cleared when a player vanishes
• Hidden players are ignored for sleeping percentage checks
• Configurable damage, hunger, air, fire, and freezing protection
• Void rescue
• Short reappearance protection
• Unsafe reappearance checks with an explicit --confirm override
• Nearby safe location search where the platform can perform it safely
• State restoration only replaces values VanishSystem actually changed

• Block breaking and placement
• Entity damage and projectiles
• Item dropping and pickup
• Experience pickup
• Containers, redstone, signs, trading, breeding, leashing, mounting, sleeping, and fishing
• Buckets, fire tools, bonemeal, brushes, and shears
• Creative inventory protection
• Command allowlists or denylists
• Temporary interaction unlocks that relock themselves
• Lock, timed unlock, or one message unlock
• Confirmation oriented chat modes
• Separate unlock and bypass permissions
• Protection for configured public facing commands
• Clear warning indicators while chat or interaction is unlocked

• Silent container opening for chests, barrels, shulkers, hoppers, droppers, furnaces, brewing stands, lecterns, and ender chests
• Packet level suppression of the lid animation and the open sound, sent only to the viewers who should not see it
• A compatibility fallback when PacketEvents is disabled
• Audit records for every silent open

• Select a player manually, or choose the nearest, next, or previous target
• Follow a selected player
• Silent teleport and saved return locations
• Target information with health, food, ping, gamemode, world, and coordinates
• Optional per viewer target glow when the packet layer supports it
• Action bar, boss bar, title, sidebar scoreboard, and chat reminders
• Separate warning states for unlocked chat, unlocked interaction, or degraded network sync
• Configurable personal sounds
• Player preferences are remembered

• File storage by default
• SQLite support
• MySQL and MariaDB support through HikariCP
• Prepared statements
• Bounded asynchronous storage queue
• Ordered writes so an older save cannot overwrite a newer state
• Independent local and network state rows
• Versioned network tombstones for reliable reveals
• Hash chained audit records
• Startup schema migration
• Health probes and reconciliation
• Durable network recovery journal
• Last known good configuration on failed reload

• Velocity, BungeeCord, and Waterfall companions
• Local or network wide vanish
• Shared authoritative SQL state
• Signed and replay protected bridge messages
• Immediate invalidation hints with database polling as recovery
• Proxy side protection for supported commands, suggestions, counts, and ping samples
• Bounded queues and outage recovery

/vanish doctor checks the active hiding layers, storage health, PacketEvents state, configuration, and network synchronization. Useful if you are having issues with the plugin or suspect VanishSystem is causing issues.

For even more information, enable diagnostics and run:

/vanish debug confirm

The report is made and saved under VanishSystem's debug-reports folder.

The root command and aliases are configurable.

Command flags

VanishSystem splits its settings by responsibility, so the main config does not become one enormous file.

plugins/VanishSystem/
├── config.yml
├── messages.yml
├── announcements/config.yml
├── audit/config.yml
├── chat/config.yml
├── containers/config.yml
├── discovery/config.yml
├── ghost/config.yml
├── gui/config.yml
├── indicators/config.yml
├── movement/config.yml
├── network/config.yml
├── profiles/config.yml
├── restrictions/config.yml
├── safety/config.yml
├── target/config.yml
├── visibility/config.yml
└── language/en.yml

%vanish_is_vanished%          %vanish_state%
%vanish_profile%              %vanish_duration%
%vanish_use_level%            %vanish_see_level%
%vanish_target%               %vanish_packet_layer%
%vanish_online_visible%       %vanish_online_public%
%vanish_hidden_total%         %vanish_sync_status%
%vanish_public_chat_locked%

• The normal Bukkit layer cannot suppress every sound, particle, metadata, or team packet. Enable PacketEvents when resistance to packet inspection matters.
• Arbitrary output from /list, /who, or third party plugins is not generically rewritten. Supported target commands and VanishSystem's own output are viewer aware.
• Minecraft's legacy UDP Query response cannot be rewritten safely by this build.
• Inventory inspection is not included at all. Use a dedicated inventory plugin alongside this one.
• Audit export, Redis transport, advancement/recipe suppression, and most third party map or Discord adapters are not included.
• Per viewer glow requires PacketEvents and is disabled on Folia.
• Folia target information uses published snapshots and can lag by one refresh.
• Folia reappearance stays at the current position and uses a terrain only safety check during the synchronous state transition.
• Plain Spigot exposes fewer safe hooks than Paper, so some server list and rich message behavior falls back gracefully.

1. Install the latest version of PacketEvents.
2. Open plugins/VanishSystem/config.yml.
3. Set packetevents.enabled: true.
4. Restart the server.
5. Run /vanish doctor and check that the packet layer reports as active.

If PacketEvents is missing, disabled, or not working, VanishSystem keeps the normal hiding system and reports the reduced coverage.

1. Set storage.type: mysql on each backend.
2. Point every backend at the same database.
3. Give every backend a unique server-name.
4. Enable the network module.
5. Configure the same shared secret everywhere.
6. Install the matching Velocity or BungeeCord companion.
7. Restart the proxy and backends.
8. Check /vanish doctor and /vanishproxy status.

if (VanishAPI.isVanished(player)) {
    return;
}

if (!VanishAPI.canSee(viewer, target)) {
    continue;
}