All versions
v1.0.0
Release
Homes! v1.0.08 months ago 26
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Added
- Complete rewrite from ground up for modern Paper servers (1.21.11+)
- MiniMessage support throughout plugin—full color and formatting control via YAML, no more legacy
§codes - Particle beacon system with 13 customizable colors, per-home visibility control, and zero external dependencies
- Per-player data storage using individual YAML files (
playerdata/<uuid>.yml) instead of monolithic storage - Configurable GUIs entirely defined through simple YAML files in
menus/directory - Multi-language support with 7 built-in languages (EN, IT, ES, FR, DE, RU, UK) and extensible lang system
- Teleport warmup & cooldown with real-time action bar countdown
- Home sharing system allowing players to share homes with others
- Admin tools for server management (delete any home, force-teleport)
- Vault economy integration with optional teleport costs
- Granular permission nodes for fine-grained access control
- Tab completion for homes, colors, and subcommands
- Input validation and comprehensive error handling
Technical Improvements
- Atomic YAML writes for data safety
- Sound and particle effect system with configurable options
- Distance and world checks for beacon rendering (128-block range)
- Safe concurrent data structures for multi-threaded access
Removed
- Legacy
§color codes (replaced with MiniMessage) - Monolithic YAML file storage (split to per-player files)
- Static/hardcoded GUI layouts (now fully configurable)
Fixed
- Beacon visibility now properly player-only (no cross-player beam visibility)
- Particles render correctly on all server versions
- Proper cleanup of tasks on player disconnect
- Correct handling of world changes and dimension travel
- Safe handling of player data with concurrent access
Note: This is a full rewrite targeting modern server infrastructure. Configurations from older versions are not compatible and should be replaced with the new format.
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:VWlsaAvU:Ro5ouE0J"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VWlsaAvU:Ro5ouE0J"
}

