All versions
2.0v
Release
SetHome+ v2.0 - Patch Notes & Changeloglast week 58
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
1.20.x
1.19.x
Platforms
Paper
Spigot
Changes
π SetHome+ v2.0 - Patch Notes & Changelog
π οΈ Key Highlights & Major Improvements
-
Dynamic GUI Pagination System
- Added automated page calculation when player home counts exceed the single-page GUI limit.
- Added customizable navigation controls (Next Page & Previous Page arrows) driven fully by
config.yml. - Interactive click protection preventing players from pulling or modifying GUI items.
-
Enhanced Name Validation & Security Controls
- Duplicate Prevention: Prevents players from overwriting existing homes unintentionally and alerts them when a home name is taken.
- Configurable Name Length: Introduced
min_name_length(default: 2) andmax_name_length(default: 16) properties. - Special Character Filter: Added a strict regex pattern filter to block hazardous symbols by default (
allow_special_characters: false), while keeping an option to enable them in the config.
-
OP & Permission Bypass System
- Added the
home.allow_op_bypasstoggle insideconfig.yml. - Enables administrators or players with
sethome.bypass/sethome.limit.*to bypass standard rank quotas. - Respects strict LuckPerms node limits (
sethome.limit.<number>) when bypass is disabled.
- Added the
-
Full Localization & Code Optimization
- Entire
config.ymlstructure reorganized with descriptive english comments and organized headers. - Cleaned up deprecation warnings and updated Spigot API handlers for optimal performance.
- Entire
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:Z0V52k72:OA3o6S5z"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Z0V52k72:OA3o6S5z"
}

