Tags
Creators
Details
2.5.0
Compatibility
Changes
Changelog:
- Updated the whole mod logic, now it should work much better and stable than 1.x versions. This should resolve most, if not all, issues regarding lags or unknown behaviour of finding safe spot for players.
- Fixed wrong configuration ranges not allowing users to set negative coordinates values, fixes #1
- As of 2.0, modpack developers may adjust lower-upper values of the 'y' coordinates from -2048 to 2048, technically fixes #3
- Fixed a bunch of typos in the configuration comments
- Heavily reworked and optimized the safe spot finding algorithm, fixes #5, #6 and possibly #2.
- Improved code readability a bit.
ALWAYS do backups, here may be dragons after all.
As of this version, 1.16.5, 1.18.2, 1.19.x are deprecated. They will receive only critical bugfixes. As of this version, 1.20.1 is considered to be a LTS version. 1.21.1+ builds will come up a bit later.
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:y7cEIWv4:TldTtSRU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:y7cEIWv4:TldTtSRU"
}

