Links
Tags
Creators
Details
0.2.0
Compatibility
Changes
What's Changed
-
Universal/Player-independent flags by @T14D3 in https://github.com/T14D3/Zones/pull/9
-
Massively increased speed of locational region lookups/queries
-
Improved memory footprint of some objects
-
More configuration for caching behavior
-
Introduces "universal" flags - flags not bound to a specific player, but rather universally per region
- Examples:
- Explosion behaviour
- Mob spawning
- Fire/grass/etc spreading
- ...and more
- Examples:
-
Ability for external sources to register custom flags
v0.2.0 Hotfix for Bucket related nonsense
Full Changelog: https://github.com/T14D3/Zones/compare/0.1.9...0.2.0
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:8j3TQXmN:ouUp1B1K"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8j3TQXmN:ouUp1B1K"
}

