All versions
1.0.7
Release
Team-HomeGUI Plugin 1.0.76 months ago 13
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
[1.0.7] - 2026-05-08
Added
- XP Bar Countdown — During the teleport warmup, the experience bar now counts down visually (level number = seconds remaining, bar fill = proportion left). The bar is restored to its original value immediately after the teleport fires or is cancelled.
Fixed
- Warmup shows but teleport never happens —
HomeService.teleportHome()now callscanTeleportHome()before starting the warmup countdown. Previously the validation step was skipped entirely: the cooldown was set, the "Teleporting in N seconds…" message was sent, but the destinationLocationcould benull, so the actualplayer.teleport()silently failed or threw aNullPointerException. - Home limit bypass via EssentialsX
/sethome—EssentialsInterceptListener(priorityHIGHEST) now intercepts all/homeand/sethomeevents regardless of arguments, cancels them before EssentialsX can act, and opens our Home GUI instead. This prevents EssentialsX from writing homes to its own userdata and bypassing our home-count limits. setHome()skipped limit check —HomeService.setHome()now callscanSetHome()before writing to storage, enforcing the configured home maximum on every code path.
Changed
/home [anything]→ always opens GUI — Typing/home,/home home1, or any variant now opens the Home GUI. Players select which home to teleport to from there./sethome [anything]→ always opens GUI — Typing/sethome,/sethome myhouse, or any variant now opens the Home GUI. Players pick which slot to set from there.softdependinplugin.ymlnow includesEssentialsto guarantee correct load order relative to EssentialsX.
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:EnNzq5Gt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:G9WejUAk:EnNzq5Gt"
}

