Team-HomeGUI Plugin

[1.1.0] — Bug Fix Release

Fixed

🔴 Critical

• AdminHandler.handleAdminAdd() — admin team auto-creation always failed Previously the method called handleAdminCreate() with a mismatched args array (args[2] was the placeholder string "dummy" instead of the real password). The password check always failed, so /team admin add <player> silently broke whenever the admin team did not yet exist. The method now creates the admin team directly via TeamManager.createTeam(), skipping the redundant password validation entirely.

• HomeService.canSetHome() — economy charged before slot-limit check If a player had already reached their home limit, the old code debited their balance first and then checked the limit, causing money to be lost without a home being set. Validation order is now: name format → slot limit → economy charge. The same fix was applied to HomeHandler.handlePlayerSetHome().

• Dual cooldown maps — players could bypass home teleport cooldown The /home command (HomeHandler) wrote cooldowns to HomeManager.teleportCooldowns while the GUI (HomeService / MenuListener) wrote to CooldownManager.homeCooldowns. Because neither path read the other map a player could alternate between the command and the GUI to teleport with no cooldown delay. HomeManager.teleportCooldowns has been removed entirely. All three paths — /home command, personal-home GUI click, and team-home GUI click — now use CooldownManager exclusively.

🟡 Medium

• CooldownManager.checkTeamCooldown() — permission node teamplugin.team.nocooldown was missing from plugin.yml The permission existed in code but was never declared, so permission-management plugins could not grant it and the bypass never worked. Added to plugin.yml with default: op.

• MenuListener — wrong config key used for delete-home success message The listener looked up messages.del-success, a key that does not exist in home-config.yml. The correct key is messages.delhome-success. Players always saw the hardcoded fallback string instead of the configured message.

• saveAsyncFuture() — unsafe method still callable Both TeamManager and HomeManager kept a saveAsyncFuture() method that was documented as unsafe (causes ConcurrentModificationException with FileConfiguration). The method is now marked @Deprecated and throws UnsupportedOperationException to prevent accidental future use.

• CooldownManager.cleanupExpiredCooldowns() — never called → slow memory leak The cleanup method existed but was never scheduled. A repeating async task (every 10 minutes) is now registered in TeamPlugin.onEnable() to drain stale entries from the cooldown maps.

🟢 Minor

• AdminHandler — hardcoded § colour codes handleAdminList() and showTeamInfo() used raw § codes which bypass the plugin's colour API. Replaced with &-codes processed via TeamPlugin.color().

Added

• TeamPlugin.getCooldownManager() — public getter so handlers can share the single CooldownManager instance without reaching through homeService.

Changed

• HomeManager: teleportCooldowns map and its getter/setter removed. Old homes.yml files that contain a cooldown sub-key are silently ignored on load and not written back, providing a clean migration path.
• Version bumped 1.0.9 → 1.1.0.