ColorPrefix

ColorPrefix 1.1.1 — Minecraft 26.2 Support

Before you update

- Now requires Java 25. Paper 26.x no longer runs on Java 21 — please update your JDK before updating this plugin, otherwise your server won't start. - Target version: Minecraft 26.2 (Paper). Older versions are not supported by this build.

Changes

- Full compatibility with Paper 26.2 - Bumped to the new Paper API (26.2) and Java 25 - Updated dependencies for 26.x (LuckPerms, PlaceholderAPI) - Reviewed internal API calls against the current Paper / item-component API

Compatibility

- Minecraft: 26.2 - Java: 25+ - Required: LuckPerms - Optional: PlaceholderAPI, TAB, EssentialsX, ChatControl, CMI, VentureChat, LPC

Notes

- No config changes required — your config.yml, colors.yml, and playerdata.yml carry over unchanged. - On networks: install the plugin on every backend server, and run LuckPerms in network mode (shared DB + messaging) for cross-server prefixes.

Fixed some Issues with Permissionsystem Luckperms

Changelog

v1.0.0 — Initial Release

Features

- Color selection GUI with leather chestplate previews and glow effect on active color - 16 solid colors + 9 gradients included out of the box - Multi-stop MiniMessage gradients with per-character color interpolation - Permission-based color access (colorprefix.color.<id>, colorprefix.gradient.<id>) - Automatic multi-plugin detection — TAB, LPC, EssentialsChat, ChatControl, CMI, VentureChat supported simultaneously without any manual configuration - PlaceholderAPI expansion (%colorprefix_prefix%, %colorprefix_tag%, %colorprefix_close_tag%, %colorprefix_color_id%) - Multi-language support (EN + DE included, custom languages via lang/xx.yml) - Config auto-migration — new keys are added automatically on update without touching existing settings - /cp give <player> <id> — admin command to assign colors - /cp reset [player] — reset a player's color - /cp reload — reload config and colors without restart

Bug Fixes

- New colors added to colors.yml now correctly require their permission — permissions are registered at runtime with default: false so players without an explicit node can never access them