1.2.0
Compatibility
Changes
TakkunsHomePlugin 1.2.0
A major stability, security, and polish update. This release fixes several bugs that could prevent the plugin from working correctly, closes permission-bypass issues, and gives the home GUI a significant visual upgrade.
Fixes
-
Fixed a critical startup issue caused by an internal wiring mismatch that could prevent the plugin from building/loading correctly.
-
Permission bypass fixed: /home and /sethome now properly check permissions before running, instead of only checking inside the GUI. Revoking takkunshome.home or takkunshome.sethome now actually blocks the matching command.
-
Fixed /sethome <slot> allowing a player to save a home in a slot beyond their permitted limit, bypassing the takkunshome.limit.* permissions.
-
Fixed teleport-cancel messages (movement / damage) displaying the wrong text instead of the translated message for the player's language.
-
Fixed a small memory leak where pending home-deletion confirmations were never cleared when a player disconnected.
-
Hardened the home GUI against inventory drag exploits.
-
Removed remaining calls to deprecated Paper API methods; the plugin now builds cleanly with zero deprecation warnings.
New
-
/home reload — reload config.yml on the fly without restarting the server (requires the new takkunshome.reload permission).
-
Live coordinates & world name are now shown directly on each home item in the GUI.
-
Visual delete confirmation — clicking delete now turns the item into a TNT icon with a warning message; it safely reverts if you don't confirm within 5 seconds.
-
Redesigned GUI: two-tone border, color-coded home slots, and a refreshed title showing your current home count.
-
Added sound feedback when opening/closing the menu and when arming a delete confirmation.
-
takkunshome.limit.4 and takkunshome.limit.5 permissions are now registered in plugin.yml, and the default config ships with default-max-homes: 3 so the permission-based home limit feature is visible out of the box.
Notes
-
Default home limit changed from 5 to 3 (homes.default-max-homes) so server owners can offer extra slots via permissions; adjust this in config.yml if you want everyone to have 5 homes immediately.
-
No player data migration needed — existing home files are fully compatible.
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:hjTcW6Ic:o1OBE58O"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hjTcW6Ic:o1OBE58O"
}

