1.1.2
Compatibility
Changes
๐ Trail Mod โ Changelog
๐ Trail Mod โ Changelog
Welcome to the Trail Mod update history. Here you can find details about the latest changes, features, and improvements.
๐ ๏ธ Version 1.1.2
Polishing & Fixes
๐ Bug Fixes
- True Independence: Trail rendering is now strictly controlled by its toggle. Disabling the Trail will no longer affect other visuals, and vice-versa.
- Dynamic Health: Improved robustness of the Health-based hitbox coloring (SafeMaxHP check).
- Config UI: Clarified tooltips for Dynamic Rendering.
๐ง Version 1.1.1
Fixes & Refinements
๐ ๏ธ Key Fixes
- Feature Independence: Fixed an issue where PvP features (Spacing, Hitboxes) wouldn't render if the Trail was disabled. You can now use any feature individually!
- Dynamic Color: Fixed Player Health tracking for hitboxes (Green -> Red gradient). (May not work in process...)
- Animations: Fixed China Hat animations (Spin/Bob) not working correctly. Added "Bob Range" setting. (May not work in process...)
โจ Visual Updates
- China Hat: Renamed "Cone Hat" to "China Hat" and improved configuration options.
๐ Version 1.1.0
Streamlined Configuration & Enhanced PvP Visuals
โจ New Features
โ๏ธ PvP Enhancements
- Permanent Hitboxes: Added option to keep hitboxes visible at all times, not just when close.
- Dynamic Health Colors: Hitboxes now change color (Green -> Red) based on player health.
- Spacing Improvements: Refined spacing circle rendering and added more style options.
โ๏ธ Configuration Overhaul
- Global Layout: Every visual element now has a dedicated On/Off toggle.
- Master Switch: Use the "Mod Enabled" toggle in General settings to instantly turn off all mod effects.
๏ฟฝ Visual Updates
- No Screen Fire: Optimized default settings for minimal fire obstruction.
- Full Bright: Correctly integrated into the new config system.
๐ ๏ธ Fixes & Technical
- Cleanup: Removed unused legacy GUI code to improve performance and stability.
- Optimization: Improved rendering logic for trails and auras.
Stay visual, stay winning.
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:oEHBR1Eb:rJQkq62o"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:oEHBR1Eb:rJQkq62o"
}

