1.0.0
Compatibility
Changes
A professional, high-performance teleportation system for your Minecraft server.
Ultimate Sethome is designed to provide players with a seamless way to manage their home locations through a beautiful, intuitive Graphical User Interface (GUI). With built-in anti-cheat measures and customizable countdowns, it's the perfect addition to any Survival, Skyblock, or SMP server.
✨ Key Features
📦 Advanced GUI Menu: Manage all your homes in a 54-slot chest interface with custom glass borders (Ender/Void Style).
🛡️ Anti-Steal Protection: Hardened GUI logic prevents players from taking items out of the menu – 100% secure.
⏳ Flexible Countdown Modes: Choose how players see their teleport timer:
TITLE: Big, bold text in the center of the screen.
BOSSBAR: A sleek progress bar at the top of the screen.
CHAT: Classic, clean messages in the chat box.
🚫 Movement Detection: Teleportation cancels instantly if the player moves, preventing easy escapes from combat.
💎 Rank-Based Limits: Set different home limits for different players (e.g., Default: 3, VIP: 10, Admin: 999).
🎨 Fully Customizable: Everything from messages, sounds, and particle types to the HEX colors in the console banner can be changed in config.yml.
| Command | Description | Title 3 |
|---|---|---|
| /sethome <name> | Set a new home at your location | ultimatesethome.use |
| /home | Open the Home Management GUI | ultimatesethome.use |
| /sethome reload | Reload the plugin configuration | ultimatesethome.admin |
Limits Permission: To grant higher home limits, use: ultimatesethome.limit.<group_name>
🛠️ Installation:
-
Download Ultimate sethome
-
Drop it into your plugins folder.
-
Restart your server.
-
Configure everything in config.yml
Created by GraSter1234
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:K8crCNJL:iZU3L07C"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:K8crCNJL:iZU3L07C"
}

