Tags
Creators
Details
4.6.2
Compatibility
Required content
Changes
HuskHomes 4.6.2 improves the /phome command syntax to be more user-friendly.
/phomenow accepts just thenameof a publicly-set home- You no longer need to pass the owner's name
- If multiple homes with the same name by different users are public, executing this command will bring up a public home list filtered to homes of that name to allow the user to click through
- TAB completion will now suggest public homes by their name for easier navigation, except in cases where there are delicately-named public homes
- Added teleportation invulnerability (off by default), courtesy of @ProdPreva1l (#515)
- This lets you configure a period which players will temporarily be invulnerable for after teleporting
- Added additional permissions for changing a home/warp's name, description, or location (
huskhomes.command.edit(home|warp).(rename|description|relocate)) - The privacy status of a home will now be displayed in
/homelist, courtesy of @ProdPreva1l (#577) - Changed date/time formatting so that it is now based on your server's system locale (#599)
- Whether teleport warmups should be cancelled due to movement/damage is now configurable (#564)
- Fixed an issue with
/tppermissions requiring theotherpermission for self-teleports (#575) - Fixed renaming a home/warp allowing existing homes/wraps to be overwritten (#594)
- Fixed players not being dismounted from ridable entities/ejecting passengers before a global teleport server change (#555)
- Fixed interactive menus failing to work properly for users who had consecutive underscores in their usernames or home names (#568)
- Updated the Simplified Chinese (zh-cn) locales, courtesy of @jhqwqmc (#576, #582, #583)
- Updated the Turkish (tr-tr) locales, courtesy of @WinTone01 (#596)
To update, just drag+drop. You should regenerate your locales file (message-xx-xx.yml) for this release as their are locale changes.
Optional dependencies
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:J6U9o3JG:F7Op1Uwq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:J6U9o3JG:F7Op1Uwq"
}

