1.5.6
Compatibility
Changes
Home Point: Bukkit Release (v1.5.6)
🌟 Initial Bukkit / Spigot / Paper Release!
Home Point has officially been ported to run as a native server plugin! You no longer need Fabric or Forge to enjoy the best, most elegant interactive teleportation system.
Just drop the .jar into your plugins/ folder!
💻 Universal Compatibility
- One File for All: Due to deep integration with the core Spigot API, this single
.jarfile is natively compatible with EVERY server version from1.8.9all the way up to1.21.11. You do not need to download different files for different versions! - Full support for
Spigot,Paper,Purpur, andBukkit. - Zero Client Mods Required: Absolutely everything works server-side.
✨ Features Included in this Release
- Clickable Chat UI: We built the interactive chat menus using the
BungeeCord Chat APIto ensure every player sees beautiful[TP],[Ren],[Del], and[Share]buttons. - Smart Target Selectors: Even if you are running an ancient
1.8.9server, our custom command parser lets you use@a,@p, and@rto share your homes globally!- Example:
/home share "Base" @a
- Example:
- Advanced Configuration (
home_mod.json):homes_limit_default/homes_limit_vip/homes_limit_admin- Anti-PvP combat locking (prevents
/homelogic during fights) - Teleport warmup delays & move cancellation
- Dimension blacklists/whitelists
⚙️ How limits work on Bukkit:
Instead of specific VIP permissions modules, the limits fallback simply:
- Operators (
/op) bypass all restrictions (if enabled in config). - Players with standard OP permissions get
adminlimits. - Default players get the standard quota.
Enjoy the ultimate home teleportation experience on your Spigot/Paper server!
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:Sq9mzc08:fZGhKoH1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Sq9mzc08:fZGhKoH1"
}

