2.4
Compatibility
Changes
feat: v2.4 - modular multi-platform adapters (Folia, Paper, Purpur, Spigot, Bukkit 1.13 - 26.3+)
- Implement modular adapter system: FoliaPlatformAdapter, PaperPlatformAdapter, SpigotPlatformAdapter
- Dynamic platform and server version detection (1.13 - 26.3+)
- Update plugin.yml api-version to 1.13 with folia-supported: true
- Rename build output artifact to homes-${project.version}.jar (homes-2.4.jar)
- Decouple GUI and teleportation engines from platform-specific APIs
- Update documentation and fix unit test suite
⚠️ Testing & Stability Notice
Please note that this release features newly updated cross-version and Folia adapters and has not yet undergone extensive production testing across every possible server environment.
If you encounter any bugs, unexpected behavior, or console errors, please report them to our support mail: nothingflaresuport@gmail.com. Your feedback is greatly appreciated!
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:vOKFjt5I:RwfJYpaL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vOKFjt5I:RwfJYpaL"
}

