Navigation Menu

Skip to content

Instantly share code, notes, and snippets.

@RoboMWM
Last active January 24, 2016 01:06
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save RoboMWM/30f4484a904444c6d9ee to your computer and use it in GitHub Desktop.
Save RoboMWM/30f4484a904444c6d9ee to your computer and use it in GitHub Desktop.

The plugin does not support plugins like HealthBar,ColoredTags (or plugins with prefix/suffix tags) because they are 'selfish' in terms of handling the scoreboard. This can not be fixed without editing those plugins. However AnimatedNames is fully supported.

Spoiler: Geeky explaination:

The way bukkit is made is that every player has 1 scoreboard with different slots for the sidebar, team name, ... However most plugins do not respect this. They create a new scoreboard every time they refresh the player's score, this works and was until recently prob the most common way to refresh a scoreboard. However I am against it since it is not the way it is meant to be. The reason most developers chose not to use the same scoreboard again is because they have to reset/overwrite the previous scores what could be laggy and hard. However both with and without the antiflicker option my mechanic won't cause lagg so that is not a problem for me.

AnimatedNames and FeatherBoard both use the player's scoreboard that is available. They only create a new scoreboard on login but after that the normal refresh rate will pick up and continue to use the same scoreboard.

Why not just continue with the scoreboard that HealthBar creates? The scoreboard healthbar creates is the same for all players (not good). This is not a problem for that plugin because the scoreboard contains multiple teams. However If I would use the same scoreboard then healthbar for this plugin then the scoreboard would be the same for all players.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment