Tags
Creators
Details
0.2.1
Compatibility
Changes
-
You might have noticed, that some dungeons might be built in the air, instead of underground. This has been fixed now.
-
Additionally an improved config manager has been integrated, which does adjust your current config file with any new parameters that have been added (no need to delete the old file or manually add new infos).
-
As an Opt-In Option, you can can enable an api_reporting (can be enabled in your config.yml under api_exploring -> enabled by setting it to "true"), which will report to me any entity Gemini might tell you for creation, but the logic has not been implemented yet. This will help me to implement new features faster. Why does this feature is Opt-In? Just because I like privacy, my Webserver will know your servers IP and an UUID that is generated of your server, when you enable this feature.
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:GkO7MnF7:kmzuSYpf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GkO7MnF7:kmzuSYpf"
}

