Tags
Creators
Details
1.2.0
Compatibility
Changes
What's new
- Added optional concurrent conquest matches for non-overlapping profiles.
- Active conquests can now be restored after a restart or plugin reload.
- Added
ALL_OWNERcommand recipients, including known offline town and nation members. - Added recipient limits and tick-based batching for large command rewards.
- Added profile-aware conquest commands and API methods.
- Added rotating action bars for players involved in multiple matches.
Compatibility
- Supports Minecraft 1.21.x through 26.2.
- Built as one Java 21 JAR for Paper, Purpur, and Leaf.
- Spigot support remains best effort.
- Use Java 21 for Minecraft 1.21.x.
- Paper 26.1 and newer require Java 25.
Updating
Concurrent matches are disabled by default, so existing behavior stays the same. Missing configuration options are added automatically without replacing your current values.
Offline reward commands must run through the console and accept an offline player's name or UUID.
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:IdhAg76d:tTytW2YZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:IdhAg76d:tTytW2YZ"
}

