All versions
1.0.6
Release
Team-HomeGUI Plugin 1.0.66 months ago 21
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
[1.0.6] - 2026-05-07
Added
- Team SetHome Command - Team owners can now set shared team homes with
/team sethome - Team Owner Disband - Team owners can disband teams by using
/team leave - Enhanced PlaceholderAPI - Added 18 new placeholders for teams and homes
- GUI Color Improvements - Visual distinction: cyan (ready), gray (unset), black (no permission)
- Missing Messages - Added "owner-cannot-leave" and "team-sethome-success" messages
Changed
- Major Architecture Refactoring - Complete code quality improvement following SOLID principles
- Eliminated God Class - TeamCommand.java reduced from ~400 lines to ~100 lines, now only handles routing
- New Service Layer - Created HomeService, CooldownManager, TeamValidator for better separation of concerns
- Handler Refactoring - Moved chat, color, and list logic from TeamCommand to dedicated handler classes
- Code Deduplication - Unified cooldown management and home access logic across the codebase
- Type Safety - Created GUISlots enum to eliminate magic numbers and prevent GUI slot errors
- Validation Centralization - TeamValidator provides consistent team name validation with offensive word filtering
- Memory Management - Improved performance with better object lifecycle management
- Default Warmup Time - Set to 5 seconds instead of 0 for better teleport experience
Fixed
- Message System - All placeholders now work correctly with proper config separation
- Personal Home Messages -
/sethomenow shows correct personal home messages instead of team messages - Config Issues - Fixed missing messages that caused "message not found" errors
- Placeholder Conflicts - Personal homes use home-config, team messages use team-config
- Team Home Messages - Fixed team sethome functionality and messaging
- Owner Leave Functionality - Team owners can now properly disband their teams
Enhanced
- PlaceholderAPI Integration - Added comprehensive placeholders:
- Team:
%team_name%,%team_colored_name%,%team_role%,%team_count%,%team_has_team%,%team_is_owner%,%team_is_admin%,%team_owner%,%team_has_home%,%team_home_world%,%team_home_x%,%team_home_y%,%team_home_z% - Homes:
%team_homes_count%,%team_homes_max%,%team_homes_list%,%team_has_homes%
- Team:
- GUI Visual Experience - Better color coding for different home states
- Code Maintainability - Better code organization and single responsibility principle
- Developer Experience - Clearer code structure and better documentation
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:G9WejUAk:EPaCcoij"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:G9WejUAk:EPaCcoij"
}

