Links
Tags
Creators
Details
v2.6.1
Compatibility
Required content
Changes
Armor glow Allies inside the zone are highlighted with the color from relationArmor.allies.color. Enemies inside the zone are highlighted with the color from relationArmor.enemies.color. Works per-viewer through equipment packets and does not touch scoreboard, tab, nametag, prefix/suffix. Configured separately for each zone through relationArmor. Regular player glowing inside the zone Added zoneGlow.enable. If enabled, all valid players inside an active zone receive the glowing effect. When leaving the zone or when the event ends, the previous glowing state is restored. Minimum group players required for capture Added settings.hclans.minPlayersInZone and settings.towny.minPlayersInZone. Scoring method selection Added settings.scoringType. TIME = points are gained for staying inside the zone. KILLS = points are gained for killing players from another clan/town inside the zone. Added settings.killPoints. Multiplier and pauseCapture Added settings.multiplier. If true, the more players from a clan/town are inside the zone, the faster points are gained. Added settings.pauseCapture. If true, time-based points are not awarded while different clans/towns are inside the zone. Point ownership After a victory, the owner of the point is saved: clan, town, or player. The player who earned the most points during the latest event is also saved. WorldGuard access for the winner Added regionAccess. The winning clan/town is added to the members of the point region. Optionally sets use, interact, and chest-access flags for members. Teleport to a captured point /clan forpost works for HCLANS. /t forpost works for TOWNY. Top and owner placeholders %hcaptureevent_wins_<zone>capitan<1-10>name% (capitan must have underscores before and after it!) %hcaptureevent_wins_<zone>capitan<1-10>vault% %hcaptureevent<zone>capitan% %hcaptureevent<zone>_capitan_player% Towny PvP for one nation Fixed all known bugs.
Optional dependencies
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:oO7jVWwf:8NrKDeql"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:oO7jVWwf:8NrKDeql"
}

