Links
Tags
Creators
Details
Licensed MIT
Published 7 months ago
Updated last month
All versions
1.0.0
Release
StatTweaks 1.0.0last month 22
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.9
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
StatTweaks - Changelog
[1.0.0] - 2026-07-11
✨ Features
- ✅ Item Adjustments: Modify damage, attack speed, durability, efficiency, stack size and more
- ✅ Entity Adjustments: Change max health, speed, attack damage and detection range of any mob
- ✅ Data Components: Full support for 1.20.5+ Data Components (rarity, food, fire resistance, etc.)
- ✅ Tag Support: Apply changes to entire groups of items or entities using tags (
#minecraft:swords,#minecraft:skeletons) - ✅ Hot-Reload: Use
/stattweaks reloadto apply changes instantly - ✅ Base Display Mode: Option to see exact final values in tooltips instead of relative bonuses
- ✅ Mod Compatibility: Full support for modded items and entities from any mod
🎯 Supported Versions
- Minecraft 1.21.9
- Fabric (requires Fabric API)
- NeoForge
🛠️ Configuration
- Single JSON configuration file:
config/CPT_StatTweaks_Config.json - Dynamic stat modifications without rewriting code
- Support for both vanilla and modded items/entities
- Tooltip mode selection (relative or base display)
📋 Commands
/stattweaks reload— Reloads configuration and applies changes (Permission Level 2/OP required)
⚠️ Known Issues & Limitations
- Minecraft 1.21.9: The
/stattweaks reloadcommand does not work correctly. You must exit and re-enter the world to apply any changes to the JSON configuration - Some durability changes are visual only on already-created items
- Requires installation on both server and clients for proper synchronization
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:w71Ine2C:UiJK4ZUg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:w71Ine2C:UiJK4ZUg"
}

