Tags
Creators
Details
1.0.0
Compatibility
Changes
This is a very early development alpha, shared a while ago to Midnight to test it on GhostLand. It's HIGHLY DISCOURAGED to play on this version, due to the following game-breaking bugs:
- It's mislabeled as
0.1, even though, as far as its SemVer compatibility goes, this version should be1.0.0(since the next version,1.0.1, didn't change the API). - The proximity-based village search algorithm was completely broken in this version in multiple ways.
It's for all intents and purposes a mid-dev build that just so happened to „escape into the wild”, and is only published on Modrinth (also available on GitHub) for the sake of easier indexing on GhostLand's end. Don't play it, please. (*tho if you decide to blatantly ignore our pleas, at least use Java 25, otherwise your game will crash)
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:xSL86cA9:a5CffrkI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xSL86cA9:a5CffrkI"
}

