Tags
Creators
Details
Beta-5.0
Compatibility
Changes
[Added] Headshot Detector ā Added a functional headshot system and balanced the Operator's base damage.
[Added] New Ultimates ā Implemented Ultimate abilities for Clove and Raze.
[Added] Resource Pack ā Added full support for Resource Pack version 4.0.
[Added] Refund System ā Added a weapon selling/refund system to the buy phase.
[Added] New Shop Design ā Redesigned the shop layout (prepared for future weapon additions).
[Added] Team Distinction ā Enhanced team visibility with colored nametags and color-coded leather helmets.
[Added] New Weapons ā Added Sheriff and Ares to the armory.
[Added] Command Restrictions ā Active players can no longer execute commands from other plugins.
[Added] Map Lock ā In-game players are restricted from joining other maps.
[Added] Viper's Pit Buff ā Enemies now correctly receive the glowing effect inside Viper's Ultimate.
[Fix] Ability Reworks ā Implemented completely new, smoother mechanics for Phoenix's Wall and Gekko's Thrash.
[Fix] Visual Overhaul ā Upgraded particle visuals for Killjoy's, Sova's, and KAY/O's Ultimates.
[Fix] Ultimate Points Cap ā Ultimate charge is now strictly capped at a maximum of 5 points.
[Fix] Command Security ā Commands /val agent, /val team, and /val shop can now only be used during specific game phases.
[Fix] Tour De Force Fix ā Activating Chamber's Ultimate no longer clears the Spike item slot from the inventory.
[Work In Progress] Adding and balancing more weapons.
[Work In Progress] Creating more game modes (e.g., Swiftplay).
[Work In Progress] Enhancing and adding more immersive sounds to the Resource Pack.
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:A439swqk:OCalD4YQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:A439swqk:OCalD4YQ"
}

