Tags
Creators
Details
3.0.0-alpha.11+1.21.1-neoforge
Compatibility
Required content
Changes
TaCZ Tweaks V3 Alpha
Status: Feature parity with V2; feature incomplete for V3
It's marked as alpha because it's still feature incomplete, not because it's unstable per se
The config file will be migrated automatically; this version should serve as a drop-in replacement
Summary of Changes
- New logo
- Complete rewrite
- Multi-loader, multi-version support (
1.20.1-forge,1.21.1-neoforge,1.20.1-fabricand1.21.1-fabric) - Reorganized config screen and config structure
- New attributes system (modify damage, disable guns, etc.)
- New status effect (disarm)
- New command (
/tacztweaks refill_ammo [<targets>]) - New options (Sable/Aeronautics compat, Cuffed compat, bolt key, etc.)
Planned Features
- New overhauled and much more capable data pack system
- More attributes (suggestions welcome!)
- More commands (suggestions welcome!)
Changes Over 3.0.0-alpha.10
- TaCZ 1.2.0
- Removed the unload key and pitch lower/upper limit option as they're now implemented in the base mod
- Added new weight modifier config options
- Added a new
suppressorsHideDeathMessagesoption - Added a new option for Apothic Attributes compatibility
- Valkyrien Skies and Sable compats are now enabled by default
- Fixed
constantandwhizzbullet sounds not working at all - Fixed some datapack features acting weirdly with Sable active
- Fixed incompatibility with Sound Physics Remastered 1.5.2
- Fixed config synchronization not working correctly on LAN servers
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| tacz-tweaks-3.0.0-alpha.11+1.21.1-neoforge-sources.jar | Unknown | 2.25 MiB |
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:H8peNuJG:C0G30tdA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:H8peNuJG:C0G30tdA"
}

