HomeJavaModsGlowPlayersPro
GlowPlayersPro

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.

Banner

Presentation of GlowPlayersPro plugin showing a player with a neon effect.

Features

Commands & Permissions

Command Description Permission
/glow Toggles default glow glowplayers.use
/glow <color> Sets a specific color glowplayers.use
/glow off Removes own glow glowplayers.use
/glow neon Starts rainbow effect glowplayers.neon
/glow off <player> Removes glow from others glowplayers.admin
/glow reload Reloads configurations glowplayers.admin
/glow clearall Clears all plugin data glowplayers.admin

Configuration

Key options in config.yml:

Option Default Description
language en Language file to load (en or pt)
settings.default-color WHITE Color used both for auto-glow on join and for /glow with no arguments
settings.default-glow-enabled false Automatically apply the glow when a player joins
settings.neon-speed-ticks 10 NEON cycle speed (20 ticks = 1 second). Lower is faster
settings.neon-colors rainbow Choose and reorder the colors the NEON effect cycles through (standard colors only)
settings.cooldown-seconds 0 Cooldown between glow changes per player (0 disables it). Admins bypass
settings.use-teams true Let the plugin manage scoreboard teams. Set to false to let TAB color the glow instead

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
    

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:

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
Quick facts

Install steps are the general flow for this file type — How to install Minecraft Java mods & modpacks walks through it step by step.

Verified by MCModsHub

These come from our own check of the pack file, not from the source page.

Explore more