GlowPlayersPro

Lightweight, fully customizable player glow effects built on Minecraft's native Scoreboard API — no packets, no lag. Pick from 16 colors, enable an animated Neon mode, and integrate seamlessly with PlaceholderAPI and TAB, all with full multi-language support.

Features

• 16 Native Colors:

  BLACK	DARK_BLUE	DARK_GREEN	DARK_AQUA
  DARK_RED	DARK_PURPLE	GOLD	GRAY
  DARK_GRAY	BLUE	GREEN	AQUA
  RED	LIGHT_PURPLE	YELLOW	WHITE

• Neon Mode — animated rainbow effect that cycles through colors smoothly. The color sequence is fully configurable via neon-colors

• PlaceholderAPI Integration — expose %glowplayerspro_color% for TAB and other plugins

• TAB-friendly — optional use-teams toggle hands color control to TAB to avoid scoreboard conflicts

• Per-player Cooldown — optional anti-spam cooldown between glow changes (cooldown-seconds), with admin bypass

• Multi-language Support — English (en.yml) and Portuguese (pt.yml) included. Easily add your own

• Persistence — saves player glow states and reapplies them on join or respawn

• Legacy & Hex Support — messages support both &a and &#FFFFFF formats

• Sound Feedback — optional audio effects with configurable volume and pitch

• Config Versioning — warns you when your config.yml is outdated so you never miss new options

Commands & Permissions

Configuration

Key options in config.yml:

Installation

1. Place the .jar in your plugins folder
2. Restart your server
3. Using TAB? See TAB Integration below

TAB Integration

Glow color is controlled by scoreboard teams, and only one plugin can manage them at a time. When TAB is installed it takes over team management — and therefore the glow color. To make the two work together:

1. In GlowPlayersPro's config.yml, set settings.use-teams: false so the plugin stops managing teams and lets TAB drive the color

2. Install PlaceholderAPI

3. In TAB's groups.yml, place %glowplayerspro_color% at the very end of the player's tagprefix — it must be the last color code in the prefix:

   _DEFAULT_:
     tagprefix: "%luckperms-prefix%%glowplayerspro_color%"
     customtabname: "%glowplayerspro_color%%player%"   # optional: colors the tablist name
   

• tagprefix (nametag above the head) is required — its last color becomes the glow color
• tabprefix (tablist) has no effect on the glow; don't put the placeholder there
• customtabname is optional and only colors the name shown in the tablist

Per-group overrides: if a group defines its own tagprefix (e.g. Owner, Player), it overrides _DEFAULT_. You must append %glowplayerspro_color% at the end of each of those groups' tagprefix too, or the glow will be locked to whatever color that prefix ends with.

Because the glow uses the nametag team color, turning on a glow also tints the player's name above their head with the same color. This is how Minecraft scoreboard teams work, not a bug.

Applying changes with TAB (/glow reload)

/glow reload fully reloads GlowPlayersPro, and the %glowplayerspro_color% placeholder returns the new value immediately. However, TAB caches PlaceholderAPI values and only re-reads them on its own refresh interval, so a color change may not show in TAB right away — this is why it often "only updates after a server restart" (a restart makes TAB start fresh).

To apply changes without restarting the server:

• Quick fix: run /tab reload after /glow reload — this forces TAB to re-read the placeholder.

• Permanent fix: give the placeholder a short refresh interval in TAB's config.yml (path may vary by TAB version, usually under placeholderapi-refresh-intervals):

  placeholderapi-refresh-intervals:
    "%glowplayerspro_color%": 500
  

  With this set, TAB reflects glow color changes on its own within ~0.5s, with no reload needed.

Upgrading

New versions may add options to config.yml. Because Minecraft does not merge new keys into an existing file automatically, the plugin will keep working with sensible defaults, but new options won't appear in your file. When you see an "outdated config" warning in the console, do the following to get the latest options:

1. Back up your current config.yml
2. Delete it
3. Restart the server to regenerate a fresh, fully-commented config
4. Re-apply any custom values from your backup