-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
Yes. TabPlayerHider only removes players from the tab list. Their skin, nametag, and physical in-game presence are completely unaffected. Other players can still see and interact with them in the world.
This was a known issue that is now fixed. The plugin uses two layers:
- A Netty packet interceptor that catches every outgoing
PlayerInfoUpdatepacket and immediately follows it withUPDATE_LISTED=falsefor hidden players - A fallback scheduler task (10-tick delay) on
PlayerChangedWorldEventthat re-hides bots after dimension transitions
If you are on an older version and still see this, update to 1.0+.
Yes, both are Paper forks and are compatible.
No. The plugin uses Paper-specific NMS (Mojang-mapped) internals. It will not load on Spigot.
No. Folia has a different threading model. The plugin is not Folia-compatible.
The plugin hides the player from the tab list but their name still shows up at the top of the list sometimes.
This can happen in some clients when the player count header is cached. The player count in the tab header may still reflect the total server count. The actual player entries (names/rows) are hidden.
Check:
- The name in
config.ymlis exactly the in-game name (case-sensitive) - You ran
/tph reload(or restarted) after editing the file - The plugin is enabled (
/tph status)
Yes. The plugin doesn't care whether the hidden player is human or a bot. Any player name can be added to hidden-players.
Hidden players do not see themselves as missing — their own client shows them normally. The hiding only affects how they appear to other clients.
Yes. The hidden-players list and enabled state are saved in config.yml, which persists across restarts.
The plugin installs its own Netty handler directly and does not conflict with ProtocolLib or PacketEvents in general. If you notice any issues, please open an issue on GitHub.