Tags
Creators
Details
2.1.4-(1.21.11)
Compatibility
Required content
Changes
Additions
---{==========}---
Overhauled Impact Frame Config Menu:
- -{ Frame Background Opacity — Adjust background visibility
- -{ Frame Opacity — Fine-tune frame transparency
- -{ Unlimited Frame Amount — Remove caps on frame generation
General Settings Expansion:
- -{ Stats After Fight
- -{ Duck Music On Pause
- -{ Battle Score
- -{ Scoring Difficulty
---{==========}---
PvP Music System
Master Audio Controls:
- -{ Master Volume Slider
- -{ Player Detection Radius Slider
- -{ 5 Dynamic Tiers of Music
- -{ Tier HUD Display
Tier Configuration & Testing:
- -{ Respective Tier On/Off buttons
- -{ Respective Tier Volume slider
- -{ Hits Till Escalate slider
- -{ Time Till De-escalate slider
- -{ Fade Length to Tier (Value)
- -{ Preview (Tier)
- -{ Test Up to Tier (Tier)
- -{ Test Down to Tier (Tier)
---{==========}---
That’s mainly it for additions, now going on to bug fixes.
Bug fixes:
- Totem pop trigger not working at all
- Impact frames not triggering due to no packet return
- Impact frames being limited to four, death frames being limited to 7
- PvP Tracker not ending with certain death events
- PvP Tracker tracking non player entities, creates a phantom fight that doesn't end on either players deaths.
- Stretch To Fill not changing anything at all
- Tier HUD not displaying anything
- Frames being delayed from event triggers being slow as sludge
- Kill sounds being delayed from event triggers being slow as sludge
- Just in general if there was a bug you encountered in 2.1.3, its fixed.
forgot to add this but it also works with any server, and almost every pvp type
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:SpOsQ3y2:ALJMxp1D"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SpOsQ3y2:ALJMxp1D"
}

