Links
Tags
Creators
Details
Licensed MIT
Published 2 months ago
Updated 2 months ago
All versions
0.1.4
Beta
TML_Avaritia_addon-0.1.4-MC1.20.1+forge2 months ago 8
Compatibility
Minecraft: Java Edition
1.20.1
Platforms
Forge
NeoForge
Supported environments
Client and server
Required content
Unavailable version
Unavailable version
Changes
TML Avaritia Addon Changelog 0.1.4
Changes:
- Fixed the config system not working at all. AOE, kill mode, night vision, and boot speed settings are now actually loaded and applied.
- Reworked the Infinity Sword task. It now reuses TLM's built-in melee attack AI, so maids will properly find targets, chase them, and attack instead of standing around.
- Infinity Sword special effects and AOE now only trigger under the "Infinity Sword Attack" task. TLM's built-in attack task no longer triggers this addon's effects.
- AOE now follows Re-Avaritia's original rules and only hits hostile mobs by default. The "force kill mode" option now actually works.
- Reworked the Infinity Bow task. It now reuses TLM's built-in bow task AI and fixes the bug where the maid would eventually shoot in only one direction.
- The Infinity Crossbow and Infinity Trident tasks also now reuse TLM's built-in AI for their respective tasks.
- The Infinity Bow, Infinity Crossbow, and Infinity Trident tasks now only accept their matching Infinity weapons. Normal bows, crossbows, and tridents will no longer attack under these tasks.
- Bow, crossbow, and trident special effects (infinite arrows, tracer arrows, heaven arrows, lightning, etc.) now only trigger under their matching tasks. TLM's built-in tasks are no longer affected.
- Removed the extended melee reach feature. Melee range is back to TLM's original logic, which avoids interfering with the built-in attack task's targeting and chasing.
- Shortened the English task names to fix the task list UI overflowing in English.
- Optimized the Infinity Armor tick handling to reduce unnecessary state updates and avoid interfering with maid pathfinding.
- Switched the build environment to pure JDK 17 and standardized the jar file name format.
- Removed several unnecessary mixins and the access transformer. Only one bow-effect mixin remains, reducing interference with TLM's original behavior.
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:9KpB9xng:Garbr4lt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9KpB9xng:Garbr4lt"
}