Links
Tags
Creators
Details
2.0.0
Compatibility
Required content
Changes
A major overhaul of the mod’s stack-size system, configuration, and management workflow.
Major changes
- Reworked the internal stack-size override system
- Rebuilt the configuration format into a simpler single-rule list
- Added in-game commands for managing stack-size rules
- Added support for resetting configured items and tags back to their default stack size
- Added save and reload commands for explicitly controlling when config changes are written to disk
- Added filtering and paging support for listing configured rules
- Improved handling of very large stack sizes
- Improved rendering of large stack counts
- Explicit per-stack
MAX_STACK_SIZEcomponent changes are now respected - Normal Minecraft stacking behavior for differing components and damage values is preserved
- Improved compatibility when the mod is installed server-side without requiring it on the client
Config changes
The old multi-list configuration format has been replaced by a single overrides list.
Rules now use the format:
item_or_tag=value
Exact item rules take priority over tag rules. Among rules of the same type, later rules override earlier ones.
The special value default can be used to force an item or tag back to its normal Minecraft stack size.
Commands
Added /itemsstack commands for:
- Setting rules
- Removing rules
- Resetting rules to default
- Clearing rules
- Listing configured rules
- Saving the config
- Reloading the config
- Viewing command help
Config changes are applied immediately. /itemsstack save writes the current configuration to disk, while /itemsstack reload discards unsaved changes and reloads the saved configuration.
Optional dependencies
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:lMLWfLiS:k26jToJ4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lMLWfLiS:k26jToJ4"
}

