-
Notifications
You must be signed in to change notification settings - Fork 277
Description
Server version
Velocity 3.4.0, Tab Bridge on Paper 1.21.11
TAB version
TAB v5.5.0
Plugin list
Proxy:
[17:27:56 INFO]: Plugins: velocity, commandwhitelist, forcepack, luckperms, plan, proxycommandmanager, velocity-scoreboard-api, tab
Backend:
[17:19:55 INFO]: Bukkit Plugins (12):
[17:19:55 INFO]: - BetterHud, ForcePack, LuckPerms, Multiverse-Core, Multiverse-Inventories, Multiverse-NetherPortals, PlaceholderAPI, Plan, TAB-Bridge, UltimateAdvancementAPI
[17:19:55 INFO]: ViaBackwards, ViaVersion
Describe the bug
I am experiencing an issue where a Bossbar configured only for the Lobby server stays visible as a non-animated "Ghost Bar" when switching to a sub-server. This sub-server uses BetterHUD, which also utilizes Bossbar packets for UI rendering. It seems there is a conflict or a race condition between TAB's removal packet and the backend server's HUD initialization.
Expected behavior
No bossbar
Steps to reproduce
- Setup: Install TAB on the Proxy (Velocity) and TAB Bridge on all backend servers (Lobby and Challenge).
- Configuration: Configure a Bossbar in TAB that is restricted to the Lobby server (using display-condition).
- Initial State: Join the Lobby server. Confirm the Bossbar is visible and animating correctly.
- The Trigger: Switch to the server (which runs BetterHUD). BetterHUD uses Bossbar packets to render its UI elements immediately upon join.
- Observation: The Lobby Bossbar does not disappear. It remains at the top of the screen, frozen (animations stop), overlapping or sitting alongside the BetterHUD elements.
- Persistence: Switching back to the Lobby or to a server (without BetterHUD) does not fix it; often, a full disconnect from the Proxy is required to clear the "Ghost Bar."
Additional info
The issue does not occur when switching to a server without BetterHUD.
The Bossbar is correctly configured to only show in the Lobby (via world/server restrictions).
Even with TAB Bridge installed, the "Remove" packet seems to be ignored or overwritten by the client because the backend server (BetterHUD) immediately starts sending its own Bossbar packets.
Checklist
- I am running latest version of the plugin
- I have read the wiki to make sure it's not an issue with configuration
- I ticked all of the boxes without actually reading them
- I have read the Compatibility wiki page and am not trying to run the plugin on an unsupported server version / platform
- I am willing to cooperate to get this issue resolved faster, including providing any additional information requested or testing new builds