Find a SuperVanish join or player-list information leak
A player may learn that a hidden moderator is online through a join message or another plugin’s player list. Check each source of information rather than treating entity invisibility as complete concealment.
Follow the procedure
- List the surfaces ordinary players can use: tab display, list command, join messages, server-switch notices and any public map or status integration.
- Prepare a staff account that is already vanished and an ordinary observer without visibility bypass. Record whether the installed settings preserve vanish state across reconnects.
- Reconnect the staff account through the normal public route. Have the observer record the exact message, list entry or notification that reveals the account.
- Identify which plugin produced that surface. Compare SuperVanish’s supported integrations and settings with the responsible tab, join-message or proxy plugin documentation.
- Make a narrow supported change and repeat the reconnect. Test both hidden joins and normal visible joins so fixing one does not suppress all useful player notifications.
- Check reappearance and subsequent departure too. Document any unsupported external status integration rather than promising that vanish hides all network activity.
Check the result
The tested ordinary-player surfaces should follow the intended vanish policy without suppressing unrelated users’ legitimate join and quit messages. Retain the source and exact text of any remaining leak. Entity hiding and public status reporting are different systems and require separate verification.
If the result is wrong
If a third-party integration still leaks the account, disable only its relevant disclosure feature or seek supported integration guidance. Do not expose staff permissions or plugin configuration publicly while demonstrating the issue. Revert the last message-format change if it hides normal player activity.