2+mod
Compatibility
Changes
Open the new config menu by using the button in the pause screen or running the following command:
/function owg:config
You can now configure the spawn range and set the glider spawn with in this menu. You will not have to configure anything inside of the datapack.
- Fixed a critical issue which caused the glider to not be removed when the chunk with the glider spawn in it wasn't loaded
- Fixed a critical issue which caused some chestplates to get deleted in the area of the glider spawn
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:pbZnkRAp:DxCpH2fD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pbZnkRAp:DxCpH2fD"
}

