v2.5.8
This one is all about memory and performance, the stuff that was making RAM climb and big servers chug.
[1] Fixed a memory leak that made RAM slowly climb the longer the server ran. The team ender chest was kept in memory forever after it was first opened, so on a busy network it just piled up. Ender chests are now released when the last person closes them (and reloaded from the database next time someone opens it), so memory stays flat. Also cleaned up a handful of smaller leaks while I was at it: team chat / chat-spy toggles, quest progress, glow data and a few per-team timers weren't being released when a player logged out or a team unloaded. All released properly now.
[2] Big optimization to team glow on large servers. It was doing a ton of wasted work every second, comparing every player against every other player and even sending "stop glowing" packets to pairs that weren't glowing in the first place. It now only checks players on the same team and only sends a packet when something actually changes, which is a massive cut in CPU and network traffic at 500+ players.
[3] Opening a team ender chest no longer causes a tiny hitch. The item data is decoded off the main thread now, so even chests full of shulkers or heavy items open smoothly.
[4] Trimmed repeated config reads on hot paths. Every PvP hit, kill, chat message and tab-list refresh was re-reading settings from the parsed config; those values are cached now, which lightens the constant background load on a full server.
[5] More Folia polish for 1.21.11 and the 2026 line (26.1.x). A few actions (disbanding a team, reopening the ally menu) were running on the wrong region thread and could error on strict Folia; they run on the right thread now. I also went over the whole plugin and confirmed all scheduling, teleports and entity access use the correct Folia-safe paths.
[6] Added the missing team glow toggle messages (team_glow_enabled / team_glow_disabled) so /team glow no longer logs a "message key not found" warning. They're added to your messages.yml automatically.
For server admins: drop the new JAR in and restart, nothing to change. If you've had a slowly climbing RAM graph, this is the build that fixes it.
[1] Fixed a memory leak that made RAM slowly climb the longer the server ran. The team ender chest was kept in memory forever after it was first opened, so on a busy network it just piled up. Ender chests are now released when the last person closes them (and reloaded from the database next time someone opens it), so memory stays flat. Also cleaned up a handful of smaller leaks while I was at it: team chat / chat-spy toggles, quest progress, glow data and a few per-team timers weren't being released when a player logged out or a team unloaded. All released properly now.
[2] Big optimization to team glow on large servers. It was doing a ton of wasted work every second, comparing every player against every other player and even sending "stop glowing" packets to pairs that weren't glowing in the first place. It now only checks players on the same team and only sends a packet when something actually changes, which is a massive cut in CPU and network traffic at 500+ players.
[3] Opening a team ender chest no longer causes a tiny hitch. The item data is decoded off the main thread now, so even chests full of shulkers or heavy items open smoothly.
[4] Trimmed repeated config reads on hot paths. Every PvP hit, kill, chat message and tab-list refresh was re-reading settings from the parsed config; those values are cached now, which lightens the constant background load on a full server.
[5] More Folia polish for 1.21.11 and the 2026 line (26.1.x). A few actions (disbanding a team, reopening the ally menu) were running on the wrong region thread and could error on strict Folia; they run on the right thread now. I also went over the whole plugin and confirmed all scheduling, teleports and entity access use the correct Folia-safe paths.
[6] Added the missing team glow toggle messages (team_glow_enabled / team_glow_disabled) so /team glow no longer logs a "message key not found" warning. They're added to your messages.yml automatically.
For server admins: drop the new JAR in and restart, nothing to change. If you've had a slowly climbing RAM graph, this is the build that fixes it.
Resource Information
Author:
----------
Total Downloads: 477
First Release: Nov 19, 2025
Last Update: Jun 19, 2026
Category: ---------------
All-Time Rating:
Find more info at kotori.ink...2 ratings
Version -----
Released: --------------------
Downloads: ------
Version Rating:
----------------------
-- ratings