1.8
Compatibility
Changes
This update is focused on a few key points for stability.
A long-standing issue involved players getting their spawn point reset on a server where this plugin was first installed. This is no longer the case; people will reappear right where they expect it. This also makes the plugin more resilient in case of an unexpected data loss.
The bed respawn positions might not have been saved properly on servers running 1.21.5+, this has been fixed. Compatibility with servers running up to 1.21.4 has been kept.
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:DG25TOx2:UhJRrXKa"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DG25TOx2:UhJRrXKa"
}

