Vanish++

Added

• Cross-Server Vanish State Reconciliation: When a player joins a server that shares a MySQL/PostgreSQL database with other servers, their vanish state from any other server is immediately applied — no manual /vanish needed after switching. Works on BungeeCord/Velocity networks with a shared database. Stale in-memory entries for offline players are also periodically purged so no server accumulates phantom vanished UUIDs.
• Instant Proxy-Ready Vanish State on Join: Vanish state is now pre-fetched from the database during AsyncPlayerPreLoginEvent (before the player fully connects), so it is applied on the very first tick of PlayerJoinEvent with zero additional delay. On a proxy network, players switching servers appear vanished or visible to staff immediately, with no visible flicker or catch-up period.
• Native Velocity Proxy Plugin: A companion Velocity plugin (vanishpp-velocity) provides a dedicated vanishpp:proxy plugin messaging channel for real-time cross-server state sync, config push, and network-wide /vanishreload. The proxy maintains an authoritative vanished-player list and broadcasts state changes to all connected Paper servers instantly. Automatically detected on startup — servers fall back to standalone mode if no Velocity proxy is found.
• Scoreboard Timezone Offset (timezone-offset-hours): The scoreboard's %time% and %date% placeholders now support a configurable hour offset applied on top of the base timezone. Set timezone-offset-hours: 2 in scoreboards.yml to shift the displayed time forward by two hours from the base zone (supports decimals like 5.5 for IST). timezone: "default" already uses the server's system clock; the offset is applied on top of whichever zone is configured.
• ProtocolLib Missing Warning — Disabled Features List: The startup warning shown to staff when ProtocolLib is not installed now includes a [Disabled Features ▶] hover button listing all 7 features that require ProtocolLib (tab-complete scrubbing, entity packet filtering, ghost-proof spawning, scoreboard team scrubbing, server list count adjustment, silent chest animations/sounds, staff glow).

Fixed

• Mobs Looking at Vanished Players (Passive Head Tracking): Re-introduced MobAiManager with a correct implementation. The root cause of the 1.1.5 regression was that SafeLookAtPlayerGoal returned false from shouldActivate() when only vanished players were nearby — this freed the LOOK goal slot, allowing the vanilla LookAtPlayerGoal to fill it (vanilla has no vanish awareness). SafeLookAtPlayerGoal now claims the LOOK slot whenever any player is in range (returning true with a null target when all nearby players are vanished), so the vanilla goal can never activate for vanished players. A periodic 20-tick sweep also force-clears any combat targets pointing at vanished players as a safety net.
• Cross-Server Timed Rule Expiry Message Not Delivered: When a timed rule (e.g. /vrules <player> mob_targeting time 30) expired on server A while the player was already connected to server B, the notification was never shown. The fix is three-layered: (1) a PLAYER_MESSAGE packet type routes the message through the Velocity proxy to wherever the player currently is; (2) if no carrier player is available to send the packet, a __notify_expired__<rule> flag is written to the shared database; (3) a 5-second async poll on every server checks online players for pending DB flags and delivers + clears them immediately — no reconnect required. The rule revert itself always completes successfully; only the notification delivery was affected.
• ProtocolLib Async Entity Lookup Spam: getEntityFromID() was being called from ProtocolLib packet listeners on async threads (e.g. triggered by Orebfuscator), causing console spam and unsafe cross-thread world access. Entity ID to UUID resolution is now handled via a local ConcurrentHashMap cache populated at join and cleared at quit, keeping all lookups off the world thread entirely. (Thanks SimplyRan, PR #5)
• Folia Crash: Night Vision Applied from Global Scheduler: When cross-server vanish sync (Redis) applied vanish effects from the global region scheduler, calling player.addPotionEffect() and player.removePotionEffect() directly caused an UnsupportedOperationException on Folia because the global scheduler does not own any player entity's region. Night vision potion calls in applyVanishEffects, removeVanishEffects, and resyncVanishEffects are now dispatched through vanishScheduler.runEntity(), which routes to the entity's own region scheduler on Folia and to the main thread on all other platforms. (Thanks SimplyRan, PR #1)
• Silent Container Item Duplication: Opening containers while vanished could cause items to duplicate or appear as wrong state. The root cause was a snapshot-copy approach — changes were written to a copy of the inventory and synced back on close, but the sync-back could overwrite concurrent item movements (hoppers, other players) and double-count items. Containers are now opened directly against the real inventory, matching vanilla behaviour exactly.
• Storage Backend Not Applied After /vanishreload: Changing storage.type in config.yml (e.g. from YAML to POSTGRESQL) had no effect until the server was fully restarted. /vanishreload now shuts down the active storage provider and reinitializes it from the current config, making storage type changes take effect immediately.
• /vanishscoreboard Visible in Tab-Complete for All Players: The command appeared in tab-complete for players who lacked vanishpp.scoreboard, revealing the feature's existence. The command entry in plugin.yml now declares permission: vanishpp.scoreboard, causing Bukkit to hide it from players without that node.
• MobAiManager Crash on Spigot/Bukkit: MobAiManager called Bukkit.getMobGoals() — a Paper-only API — unconditionally on startup, causing NoSuchMethodError crashes on Spigot and Bukkit when the listener was registered. The manager is now only registered when the Paper API surface is confirmed present (Paper, Purpur, Folia). Mob AI goal injection and the 20-tick sweep remain fully operational on all Paper-family servers; on Spigot/Bukkit mob targeting prevention continues to work via EntityTargetEvent.

Added

• Cross-Server Vanish State Reconciliation: When a player joins a server that shares a MySQL/PostgreSQL database with other servers, their vanish state from any other server is immediately applied — no manual /vanish needed after switching. Works on BungeeCord/Velocity networks with a shared database. Stale in-memory entries for offline players are also periodically purged so no server accumulates phantom vanished UUIDs.
• Instant Proxy-Ready Vanish State on Join: Vanish state is now pre-fetched from the database during AsyncPlayerPreLoginEvent (before the player fully connects), so it is applied on the very first tick of PlayerJoinEvent with zero additional delay. On a proxy network, players switching servers appear vanished or visible to staff immediately, with no visible flicker or catch-up period.
• Native Velocity Proxy Plugin: A companion Velocity plugin (vanishpp-velocity) provides a dedicated vanishpp:proxy plugin messaging channel for real-time cross-server state sync, config push, and network-wide /vanishreload. The proxy maintains an authoritative vanished-player list and broadcasts state changes to all connected Paper servers instantly. Automatically detected on startup — servers fall back to standalone mode if no Velocity proxy is found.
• Scoreboard Timezone Offset (timezone-offset-hours): The scoreboard's %time% and %date% placeholders now support a configurable hour offset applied on top of the base timezone. Set timezone-offset-hours: 2 in scoreboards.yml to shift the displayed time forward by two hours from the base zone (supports decimals like 5.5 for IST). timezone: "default" already uses the server's system clock; the offset is applied on top of whichever zone is configured.
• ProtocolLib Missing Warning — Disabled Features List: The startup warning shown to staff when ProtocolLib is not installed now includes a [Disabled Features ▶] hover button listing all 7 features that require ProtocolLib (tab-complete scrubbing, entity packet filtering, ghost-proof spawning, scoreboard team scrubbing, server list count adjustment, silent chest animations/sounds, staff glow).

Fixed

• Mobs Looking at Vanished Players (Passive Head Tracking): Re-introduced MobAiManager with a correct implementation. The root cause of the 1.1.5 regression was that SafeLookAtPlayerGoal returned false from shouldActivate() when only vanished players were nearby — this freed the LOOK goal slot, allowing the vanilla LookAtPlayerGoal to fill it (vanilla has no vanish awareness). SafeLookAtPlayerGoal now claims the LOOK slot whenever any player is in range (returning true with a null target when all nearby players are vanished), so the vanilla goal can never activate for vanished players. A periodic 20-tick sweep also force-clears any combat targets pointing at vanished players as a safety net.
• Cross-Server Timed Rule Expiry Message Not Delivered: When a timed rule (e.g. /vrules <player> mob_targeting time 30) expired on server A while the player was already connected to server B, the notification was never shown. The fix is three-layered: (1) a PLAYER_MESSAGE packet type routes the message through the Velocity proxy to wherever the player currently is; (2) if no carrier player is available to send the packet, a __notify_expired__<rule> flag is written to the shared database; (3) a 5-second async poll on every server checks online players for pending DB flags and delivers + clears them immediately — no reconnect required. The rule revert itself always completes successfully; only the notification delivery was affected.
• ProtocolLib Async Entity Lookup Spam: getEntityFromID() was being called from ProtocolLib packet listeners on async threads (e.g. triggered by Orebfuscator), causing console spam and unsafe cross-thread world access. Entity ID to UUID resolution is now handled via a local ConcurrentHashMap cache populated at join and cleared at quit, keeping all lookups off the world thread entirely. (Thanks SimplyRan, PR #5)
• Folia Crash: Night Vision Applied from Global Scheduler: When cross-server vanish sync (Redis) applied vanish effects from the global region scheduler, calling player.addPotionEffect() and player.removePotionEffect() directly caused an UnsupportedOperationException on Folia because the global scheduler does not own any player entity's region. Night vision potion calls in applyVanishEffects, removeVanishEffects, and resyncVanishEffects are now dispatched through vanishScheduler.runEntity(), which routes to the entity's own region scheduler on Folia and to the main thread on all other platforms. (Thanks SimplyRan, PR #1)
• Silent Container Item Duplication: Opening containers while vanished could cause items to duplicate or appear as wrong state. The root cause was a snapshot-copy approach — changes were written to a copy of the inventory and synced back on close, but the sync-back could overwrite concurrent item movements (hoppers, other players) and double-count items. Containers are now opened directly against the real inventory, matching vanilla behaviour exactly.
• Storage Backend Not Applied After /vanishreload: Changing storage.type in config.yml (e.g. from YAML to POSTGRESQL) had no effect until the server was fully restarted. /vanishreload now shuts down the active storage provider and reinitializes it from the current config, making storage type changes take effect immediately.
• /vanishscoreboard Visible in Tab-Complete for All Players: The command appeared in tab-complete for players who lacked vanishpp.scoreboard, revealing the feature's existence. The command entry in plugin.yml now declares permission: vanishpp.scoreboard, causing Bukkit to hide it from players without that node.
• MobAiManager Crash on Spigot/Bukkit: MobAiManager called Bukkit.getMobGoals() — a Paper-only API — unconditionally on startup, causing NoSuchMethodError crashes on Spigot and Bukkit when the listener was registered. The manager is now only registered when the Paper API surface is confirmed present (Paper, Purpur, Folia). Mob AI goal injection and the 20-tick sweep remain fully operational on all Paper-family servers; on Spigot/Bukkit mob targeting prevention continues to work via EntityTargetEvent.

Added

• Vanish Scoreboard: A configurable sidebar scoreboard shown automatically to vanished players (vanishpp.scoreboard). Displays world, TPS, online count, coordinates, direction, biome, ping, health, food, armor, time, date, vanish level, and more. Updates coordinates in real-time on movement via ProtocolLib packet listener (with configurable cooldown). Toggle manually with /vscoreboard. Auto-shows on vanish, hides on unvanish. Configured in scoreboards.yml. Reloads with /vreload.
• /vscoreboard Command: Toggle the vanish scoreboard on/off. Requires vanishpp.scoreboard.
• Scoreboard Placeholders: Full set of built-in placeholders: %world%, %tps%, %tps_raw%, %online%, %max_players%, %vanished_count%, %x%, %y%, %z%, %direction%, %biome%, %ping%, %gamemode%, %health%, %max_health%, %food%, %armor%, %level%/%vanish_level%, %player%, %displayname%, %memory_used%, %memory_max%, %entities%, %chunks%, %time%, %date%. PlaceholderAPI supported.
• /vlist Interactive Player Names: Each player name in /vlist output is now clickable. Hovering shows the player's vanish level and world; clicking runs /vanish <player> to unvanish them instantly.
• Periodic Update Checker: The update checker now re-runs every hour in the background — not just once on startup. Staff with vanishpp.update are notified without needing a server restart.
• SQL Schema Versioning: MySQL/PostgreSQL storage now tracks a schema version in vpp_schema_version and runs structured migrations on startup, allowing for future schema changes. Schema v2 adds created_at/updated_at columns for future audit trail features.
• Real-Time Database Sync: Vanish state changes (vanish/unvanish) are now persisted to the database asynchronously, so storage I/O never blocks the main thread on join or leave. Rules and vanish state are kept in a per-player in-memory cache — pre-populated async on join and cleared on quit — eliminating database round-trips on hot event paths (block breaks, entity damage, etc.).
• Database Connection Error Notifications: When database connectivity fails, staff with vanishpp.admin or OP status are notified in-game (throttled every 5 minutes to prevent spam). Helps identify infrastructure issues without requiring log file access.
• Proxy Plugin Integration Documentation: Complete guide for proxy plugins (BungeeCord/Velocity) to read vanish state directly from the database. Includes example adapters and security best practices.

Changed

• Spectator Quick-Switch Restores Exact Gamemode: Double-shifting out of Spectator now returns the player to the gamemode they were in before entering Spectator (Creative, Adventure, Survival), not always Survival.
• DiscordSRV Fake Join/Leave Use Embed Format: Fake join and leave messages sent to Discord on vanish/unvanish now use DiscordSRV's own sendJoinMessage()/sendLeaveMessage() methods, honouring the embed, colour, avatar, and webhook settings configured in DiscordSRV's messages.yml. Previously they were always plain bold text regardless of configuration.
• Scoreboard Column Auto-Alignment: Lines containing a | separator are automatically padded so the separator lands at the same column on every line. Label widths are measured after stripping color codes. Works for any custom label length — no manual padding needed.
• Scoreboard Hides Score Numbers: Score numbers on the right side of the sidebar are hidden using Paper's NumberFormat.blank() API for a cleaner look.
• Config Defaults Hardened: All config reads now use explicit fallback defaults. Previously, deleted or missing keys would silently produce false/0 — now the intended default is always applied even on a stripped config file.
• Database Transaction Safety: removePlayerData() now uses transactions to ensure all-or-nothing deletion. Connection errors during cleanup are logged but don't partially corrupt data.
• Network Sync Idempotency: Cross-server vanish sync (Redis) now ignores duplicate messages to prevent visibility state divergence if network flakiness causes message replays.

Fixed

• Folia Crash on Startup: Folia 1.21.11 renamed the internal detection class used by the scheduler bridge, causing the plugin to load BukkitSchedulerBridge instead of FoliaSchedulerBridge. Added Bukkit.getName() as a fallback detection method. Additionally, Folia forbids ScoreboardManager.registerNewTeam() on the startup thread — team setup is now deferred to the global region scheduler, and vanishTeam usages are null-guarded for the brief window before it completes.
• Action Bar Warning Overwritten: Warning messages (e.g., "Action Blocked") shown in the action bar were immediately erased by the vanish status bar on the next scheduler tick. Warnings now display for their full intended duration before the status bar resumes.
• prevent-potion-effects Wrong Default: This setting defaulted to true in code, silently blocking all potion effects (including healing potions thrown by staff) on servers where the key was missing from config.yml. Corrected to false.
• SQL Acknowledgements Not Persisted: The vpp_acknowledgements table was missing from the MySQL/PostgreSQL schema. Persistent acknowledgements (ProtocolLib missing warning, config migration reports) were silently ignored for SQL storage users — they are now stored and respected correctly.
• SQL removePlayerData Left Stale Acknowledgements: Removing a player's data via SQL did not delete their acknowledgement rows. Stale entries could suppress future notifications for that UUID. Now cleared along with rules and level data in a single transaction.
• SQL getRules Returned Strings Instead of Booleans: getRules() returned raw SQL text values ("true", "false") instead of Boolean objects, breaking any code comparing rule values by type. Values are now parsed to Boolean before being returned.
• PostgreSQL addAcknowledgement() Syntax Error: PostgreSQL ON CONFLICT clause was incomplete, missing the constraint columns. Now correctly uses ON CONFLICT (uuid, notification_id) DO NOTHING.
• Redis Subscriber Thread Leak: The Redis subscriber thread was never gracefully shut down on plugin reload, causing lingering connections and resource exhaustion. Now properly interrupts the thread with timeout and closes Jedis resources.
• Folia Visibility Sync Thread Safety: Visibility sync task could cause ConcurrentModificationException in Folia's multi-region environment. Now uses immutable snapshots for safe iteration.
• SQL Schema Migration Idempotency: Calling init() multiple times (e.g., on reload) would fail with primary key violations. Now idempotent and safe to call repeatedly.
• Database Error Visibility: Silent database failures provided no feedback to admins. Connection errors are now logged to console and notified to staff in-game.
• DiscordSRV Advancement Leak: Vanished players completing advancements no longer trigger Discord announcements. Suppressed via AchievementMessagePreProcessEvent as a safety net in addition to DiscordSRV's native vanish check.
• DiscordSRV Death Leak: Vanished players dying no longer trigger Discord death announcements. Suppressed via DeathMessagePreProcessEvent as a safety net.

Added

• Vanish Scoreboard: A configurable sidebar scoreboard shown automatically to vanished players (vanishpp.scoreboard). Displays world, TPS, online count, coordinates, direction, biome, ping, health, food, armor, time, date, vanish level, and more. Updates coordinates in real-time on movement via ProtocolLib packet listener (with configurable cooldown). Toggle manually with /vscoreboard. Auto-shows on vanish, hides on unvanish. Configured in scoreboards.yml. Reloads with /vreload.
• /vscoreboard Command: Toggle the vanish scoreboard on/off. Requires vanishpp.scoreboard.
• Scoreboard Placeholders: Full set of built-in placeholders: %world%, %tps%, %tps_raw%, %online%, %max_players%, %vanished_count%, %x%, %y%, %z%, %direction%, %biome%, %ping%, %gamemode%, %health%, %max_health%, %food%, %armor%, %level%/%vanish_level%, %player%, %displayname%, %memory_used%, %memory_max%, %entities%, %chunks%, %time%, %date%. PlaceholderAPI supported.
• /vlist Interactive Player Names: Each player name in /vlist output is now clickable. Hovering shows the player's vanish level and world; clicking runs /vanish <player> to unvanish them instantly.
• Periodic Update Checker: The update checker now re-runs every hour in the background — not just once on startup. Staff with vanishpp.update are notified without needing a server restart.
• SQL Schema Versioning: MySQL/PostgreSQL storage now tracks a schema version in vpp_schema_version and runs structured migrations on startup, allowing for future schema changes. Schema v2 adds created_at/updated_at columns for future audit trail features.
• Real-Time Database Sync: Vanish state changes (vanish/unvanish) are now persisted to the database asynchronously, so storage I/O never blocks the main thread on join or leave. Rules and vanish state are kept in a per-player in-memory cache — pre-populated async on join and cleared on quit — eliminating database round-trips on hot event paths (block breaks, entity damage, etc.).
• Database Connection Error Notifications: When database connectivity fails, staff with vanishpp.admin or OP status are notified in-game (throttled every 5 minutes to prevent spam). Helps identify infrastructure issues without requiring log file access.
• Proxy Plugin Integration Documentation: Complete guide for proxy plugins (BungeeCord/Velocity) to read vanish state directly from the database. Includes example adapters and security best practices.

Changed

• Spectator Quick-Switch Restores Exact Gamemode: Double-shifting out of Spectator now returns the player to the gamemode they were in before entering Spectator (Creative, Adventure, Survival), not always Survival.
• DiscordSRV Fake Join/Leave Use Embed Format: Fake join and leave messages sent to Discord on vanish/unvanish now use DiscordSRV's own sendJoinMessage()/sendLeaveMessage() methods, honouring the embed, colour, avatar, and webhook settings configured in DiscordSRV's messages.yml. Previously they were always plain bold text regardless of configuration.
• Scoreboard Column Auto-Alignment: Lines containing a | separator are automatically padded so the separator lands at the same column on every line. Label widths are measured after stripping color codes. Works for any custom label length — no manual padding needed.
• Scoreboard Hides Score Numbers: Score numbers on the right side of the sidebar are hidden using Paper's NumberFormat.blank() API for a cleaner look.
• Config Defaults Hardened: All config reads now use explicit fallback defaults. Previously, deleted or missing keys would silently produce false/0 — now the intended default is always applied even on a stripped config file.
• Database Transaction Safety: removePlayerData() now uses transactions to ensure all-or-nothing deletion. Connection errors during cleanup are logged but don't partially corrupt data.
• Network Sync Idempotency: Cross-server vanish sync (Redis) now ignores duplicate messages to prevent visibility state divergence if network flakiness causes message replays.

Fixed

• Folia Crash on Startup: Folia 1.21.11 renamed the internal detection class used by the scheduler bridge, causing the plugin to load BukkitSchedulerBridge instead of FoliaSchedulerBridge. Added Bukkit.getName() as a fallback detection method. Additionally, Folia forbids ScoreboardManager.registerNewTeam() on the startup thread — team setup is now deferred to the global region scheduler, and vanishTeam usages are null-guarded for the brief window before it completes.
• Action Bar Warning Overwritten: Warning messages (e.g., "Action Blocked") shown in the action bar were immediately erased by the vanish status bar on the next scheduler tick. Warnings now display for their full intended duration before the status bar resumes.
• prevent-potion-effects Wrong Default: This setting defaulted to true in code, silently blocking all potion effects (including healing potions thrown by staff) on servers where the key was missing from config.yml. Corrected to false.
• SQL Acknowledgements Not Persisted: The vpp_acknowledgements table was missing from the MySQL/PostgreSQL schema. Persistent acknowledgements (ProtocolLib missing warning, config migration reports) were silently ignored for SQL storage users — they are now stored and respected correctly.
• SQL removePlayerData Left Stale Acknowledgements: Removing a player's data via SQL did not delete their acknowledgement rows. Stale entries could suppress future notifications for that UUID. Now cleared along with rules and level data in a single transaction.
• SQL getRules Returned Strings Instead of Booleans: getRules() returned raw SQL text values ("true", "false") instead of Boolean objects, breaking any code comparing rule values by type. Values are now parsed to Boolean before being returned.
• PostgreSQL addAcknowledgement() Syntax Error: PostgreSQL ON CONFLICT clause was incomplete, missing the constraint columns. Now correctly uses ON CONFLICT (uuid, notification_id) DO NOTHING.
• Redis Subscriber Thread Leak: The Redis subscriber thread was never gracefully shut down on plugin reload, causing lingering connections and resource exhaustion. Now properly interrupts the thread with timeout and closes Jedis resources.
• Folia Visibility Sync Thread Safety: Visibility sync task could cause ConcurrentModificationException in Folia's multi-region environment. Now uses immutable snapshots for safe iteration.
• SQL Schema Migration Idempotency: Calling init() multiple times (e.g., on reload) would fail with primary key violations. Now idempotent and safe to call repeatedly.
• Database Error Visibility: Silent database failures provided no feedback to admins. Connection errors are now logged to console and notified to staff in-game.
• DiscordSRV Advancement Leak: Vanished players completing advancements no longer trigger Discord announcements. Suppressed via AchievementMessagePreProcessEvent as a safety net in addition to DiscordSRV's native vanish check.
• DiscordSRV Death Leak: Vanished players dying no longer trigger Discord death announcements. Suppressed via DeathMessagePreProcessEvent as a safety net.

[1.1.6] - 2026-04-01

Added

• Periodic Update Checker: The update checker now re-runs every hour in the background — not just once on startup. Staff with vanishpp.update are notified without needing a server restart.
• SQL Schema Versioning: MySQL/PostgreSQL storage now tracks a schema version in vpp_schema_version and runs structured migrations on startup, making future schema changes safe and automatic.

Changed

• Config Defaults Hardened: All config reads now use explicit fallback defaults. Previously, deleted or missing keys would silently produce false/0 — now the intended default is always applied even on a stripped config file.