ВЕРСИИ (5)

### Changed - Built against PacketEvents 2.14.0, the stable release with Minecraft 26.3 support. 2.2.0 still bundled a 2.14.0 snapshot. - New project icon. - `LICENSE` is the plain GPL-3.0 text again. A source file header had ended up at the top of it. - The Maven artifact for this version is `org.inventivetalent:glowapi:2.2.1-RELEASE`.

### Added - Auto-glow by permission. With `auto-glow.enabled: true`, a player holding `glowapi.auto.<color>` glows in that color for everyone, for example `glowapi.auto.gold` on a VIP group in LuckPerms. No code and no second plugin needed. `/glowapi reload` re-applies the colors after a permission change. Only glows handed out this way are taken back, so `/glow` and other plugins keep theirs. Off by default. ### Changed - First stable release with the 26.3 color fix and the Folia support from 2.1.x, so servers on the default `release` update channel get them as well. - The Maven artifact for this version is `org.inventivetalent:glowapi:2.2.0-RELEASE`.

- Declares Folia support. GlowAPI only sends packets and never schedules world work, so nothing else had to change.

Minecraft 26.3 support. 26.3 inserted three new packets, which shifted the team packet that glowing rides on from id 109 to 111. Every earlier build is refused by PacketEvents on 26.3 and disabled on startup. Tested on a real Paper 26.3 server: the plugin enables cleanly, all glow teams are created and parsed correctly by the client, setting and clearing colours works, and the red/blue correction for clients on 26.1 and newer behaves as it should. **Why BETA:** PacketEvents has the 26.3 support merged but has not released it yet, so this build bundles the official snapshot. Nothing in GlowAPI itself changed. The next version will be a normal release built against the PacketEvents release, with no further changes. On 26.2 and older, 2.0.1 keeps working.

Fixes a packet that older clients cannot handle. `initTeam` sends a `REMOVE` before the `CREATE` so that rebuilding the glow teams really changes their colour - a `CREATE` for a team the client already knows is ignored, so without it a config change would only ever reach players who reconnect. On a **fresh join**, though, the client has never seen those teams, and clients before 1.13 look the team up and then use it without checking for null. That `REMOVE` was going out for something that never existed there. It is now only sent when the teams were created for that player before, which is exactly the rebuild case it was added for. No API change, no config change. Everything in 2.0.0 applies unchanged.