Proxy Plugin Compatibility

Proxy Plugin Compatibility

Vanish++ stores vanish state in a persistent database (MySQL or PostgreSQL) that proxy plugins and custom code can read directly - enabling cross-network vanish awareness without plugin-to-plugin messaging.

Use Case

If you have a BungeeCord or Velocity proxy and want:

• The proxy to know which players are vanished
• Cross-server vanish state awareness
• Custom integrations (e.g. a network-wide admin panel)

Database Tables

Vanish++ uses the following tables (MySQL/PostgreSQL only):

Table	Contents
vpp_players	UUID, vanish state, vanish level
vpp_rules	Per-player rule overrides
vpp_acknowledgements	Persistent per-player notification dismissals
vpp_schema_version	Internal migration tracking

Reading Vanish State

SELECT uuid, is_vanished, vanish_level
FROM vpp_players
WHERE uuid = 'player-uuid-here';

is_vanished is a boolean (tinyint 1/0 in MySQL, boolean in PostgreSQL).

Security Best Practices

• Use a read-only database user for proxy-side queries
• Never write to Vanish++ tables from external code - use a separate table for proxy metadata
• If using Redis, subscribe to the vanish sync channel for real-time events instead of polling the database

Real-Time Sync

For real-time cross-server sync (not just database polling), see Redis Cross-Server Sync.