Tags
Creators
Details
All versions
1.1.5
Release
CaptureZones 1.1.54 months ago 208
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Version 1.1.5 - [2026-07-01]
Added
- Added a trigger-based command reward engine under
rewards.command-rewards. - Added per-zone command reward triggers:
- Successful capture
- Ownership loss
- Hourly control payout
- Daily control payout
- KOTH win
- Added per-conquest-profile winner command rewards under
conquest.profiles.<profile>.winner-command-rewards. - Added command reward recipient modes:
INITIATORPARTICIPANTSONLINE_OWNERMVPRANDOM_PARTICIPANT
- Added console and player command execution modes.
- Added overall trigger chance and per-command chance.
- Added weighted command groups for selecting one reward from a configured pool.
- Added persistent per-player and per-zone/event cooldowns.
- Added cooldown persistence in
command-reward-cooldowns.yml. - Added reward conditions for minimum participation time, kills, and eligible player count.
- Added capture contribution tracking for participation time, player kills, and reinforcement kills.
- Command rewards remain disabled by default.
- Added command placeholders:
%player%%player_uuid%%owner%%owner_type%%previous_owner%%new_owner%%zone%%zone_id%%trigger%%event%%participation_seconds%%kills%
Changed
- Updated plugin release metadata to
1.1.5.
Configuration
- Added per-zone config:
rewards.command-rewards.enabledrewards.command-rewards.executionrewards.command-rewards.chancerewards.command-rewards.cooldown.*rewards.command-rewards.conditions.*rewards.command-rewards.commandsrewards.command-rewards.triggers.*
- Added conquest profile config:
conquest.profiles.<profile>.winner-command-rewards.*
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:wHLObpJS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:IdhAg76d:wHLObpJS"
}

