GlowPlayersPro
基于 Minecraft 原生记分板 API 构建的轻量级、完全可自定义的玩家发光效果——无需数据包,无延迟。从 16 种颜色中选择,启用动画霓虹模式,并与 PlaceholderAPI 和 TAB 无缝集成,同时提供完整的多语言支持。


功能
-
16 种原生颜色:
|
|
|
|
BLACK |
DARK_BLUE |
DARK_GREEN |
DARK_AQUA |
DARK_RED |
DARK_PURPLE |
GOLD |
GRAY |
DARK_GRAY |
BLUE |
GREEN |
AQUA |
RED |
LIGHT_PURPLE |
YELLOW |
WHITE |
-
霓虹模式 — 平滑循环颜色的动画彩虹效果。颜色序列可通过 neon-colors 完全配置
-
PlaceholderAPI 集成 — 暴露 %glowplayerspro_color% 供 TAB 和其他插件使用
-
兼容 TAB — 可选的 use-teams 开关将颜色控制权交给 TAB,以避免记分板冲突
-
玩家独立冷却 — 可选的防刷屏冷却时间(cooldown-seconds),管理员可绕过
-
多语言支持 — 包含英文 (en.yml) 和葡萄牙文 (pt.yml)。轻松添加您自己的语言
-
持久化存储 — 保存玩家的发光状态,并在加入或重生时重新应用
-
兼容旧版与十六进制格式 — 消息支持 &a 和 &#FFFFFF 两种格式
-
声音反馈 — 可选音频效果,支持配置音量和音调
-
配置文件版本控制 — 当您的 config.yml 过时时会发出警告,确保您不会错过任何新功能
命令与权限
| 命令 |
描述 |
权限 |
/glow |
切换默认发光 |
glowplayers.use |
/glow <color> |
设置特定颜色 |
glowplayers.use |
/glow off |
移除自身发光 |
glowplayers.use |
/glow neon |
启动彩虹效果 |
glowplayers.neon |
/glow off <player> |
移除其他玩家的发光 |
glowplayers.admin |
/glow reload |
重载配置 |
glowplayers.admin |
/glow clearall |
清除所有插件数据 |
glowplayers.admin |
配置
config.yml 中的关键选项:
| 选项 |
默认值 |
描述 |
language |
en |
要加载的语言文件 (en 或 pt) |
settings.default-color |
WHITE |
用于加入时自动发光以及不带参数执行 /glow 时的颜色 |
settings.default-glow-enabled |
false |
玩家加入时自动应用发光效果 |
settings.neon-speed-ticks |
10 |
霓虹模式循环速度(20 tick = 1 秒)。数值越低速度越快 |
settings.neon-colors |
rainbow |
选择并重新排列霓虹模式循环经过的颜色(仅限标准颜色) |
settings.cooldown-seconds |
0 |
每个玩家两次发光变化之间的冷却时间(0 表示禁用)。管理员可绕过 |
settings.use-teams |
true |
让插件管理记分板队伍。设置为 false 以让 TAB 来为发光着色 |
安装
- 将
.jar 文件放入您的 plugins 文件夹
- 重启服务器
- 如果您使用 TAB?请参阅下方的 TAB 集成
TAB 集成
发光颜色由记分板队伍控制,且同一时间只能有一个插件管理它们。当安装了 TAB 时,它会接管队伍管理——因此也控制了发光颜色。为了让两者协同工作:
-
在 GlowPlayersPro 的 config.yml 中,将 settings.use-teams 设置为 false,这样插件就不再管理队伍,而是让 TAB 驱动颜色
-
安装 PlaceholderAPI
-
在 TAB 的 groups.yml 中,将 %glowplayerspro_color% 放在玩家 tagprefix 的最末尾——它必须是前缀中的最后一个颜色代码:
_DEFAULT_:
tagprefix: "%luckperms-prefix%%glowplayerspro_color%"
customtabname: "%glowplayerspro_color%%player%" # 可选:为标签列表中的名字着色
tagprefix(头顶上方的名牌)是必需的——其最后一个颜色将成为发光颜色
tabprefix(标签列表前缀)不会影响发光;不要将占位符放在那里
customtabname 是可选的,仅用于为标签列表中显示的名字着色
按组覆盖: 如果一个组定义了它自己的 tagprefix(例如 Owner、Player),它会覆盖 _DEFAULT_。您也必须将这些组的 tagprefix 末尾追加 %glowplayerspro_color%,否则发光将被锁定在该前缀结束时的颜色。
由于发光使用的是名牌队伍的颜色,开启发光也会使玩家头顶上方的名字染上相同的颜色。这是 Minecraft 记分板队伍的工作原理,并非错误。
通过 TAB 应用更改 (/glow reload)
/glow reload 会完全重载 GlowPlayersPro,并且 %glowplayerspro_color% 占位符会立即返回新值。然而,TAB 会缓存 PlaceholderAPI 的值,并仅在自身的刷新间隔内重新读取它们,因此颜色更改可能不会立即在 TAB 中显示——这就是为什么通常“只有在服务器重启后才会更新”(重启会让 TAB 重新开始)。
要在不重启服务器的情况下应用更改:
-
快速修复: 在运行 /glow reload 后执行 /tab reload——这会强制 TAB 重新读取占位符。
-
永久修复: 在 TAB 的 config.yml 中为该占位符设置一个较短的刷新间隔(路径可能因 TAB 版本而异,通常在 placeholderapi-refresh-intervals 下):
placeholderapi-refresh-intervals:
"%glowplayerspro_color%": 500
设置此项后,TAB 会在约 0.5 秒内自行反映发光颜色的变化,无需重载。
升级
新版本可能会向 config.yml 中添加新选项。由于 Minecraft 不会自动将新键合并到现有文件中,插件将继续正常工作并使用合理的默认值,但新选项不会出现在您的文件中。当您在控制台中看到“配置文件过时”的警告时,请执行以下操作以获取最新选项:
- 备份当前的
config.yml
- 删除它
- 重启服务器以重新生成一份全新的、带有完整注释的配置文件
- 从备份中恢复所有自定义配置项
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
| 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
- Place the
.jar in your plugins folder
- Restart your server
- 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:
-
In GlowPlayersPro's config.yml, set settings.use-teams: false so the plugin stops managing teams and lets TAB drive the color
-
Install PlaceholderAPI
-
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:
- Back up your current
config.yml
- Delete it
- Restart the server to regenerate a fresh, fully-commented config
- Re-apply any custom values from your backup
评论 0
登录后参与评分
还没有评论,来抢沙发吧