Tags
Creators
Details
2.1.0
Compatibility
Changes
Added
- Optional
RelationNatureenum (FRIENDLY,NEUTRAL,HOSTILE) to the model package. EachTeamRelationconstant carries a built-in default nature which may be queried withgetDefaultNature(). - Consumer override support:
TeamRelation#setNatureOverride(RelationNature)andTeamRelation#getNature()- allows server or provider code to re-categorise a relation at runtime. PassingnulltosetNatureOverrideclears the override and restores the builtin default. Overrides are visible JVM-wide because enum constants are singletons. - Unit tests:
TeamRelationTestcovering default natures and override behaviour.
Changed
TeamsAPI.API_VERSIONbumped to2.1.0.
Migration
No behavioural changes to existing TeamRelation helpers: isFriendly() and
isHostile() remain unchanged and existing consumers require no changes. Providers
that wish to reclassify relations (for example treating TRUCE as NEUTRAL) may
call setNatureOverride(...) during initialisation.
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:2NJKwgXC:7Y1vUPMt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2NJKwgXC:7Y1vUPMt"
}

