Change Minecraft item stack sizes with a simple config file.
ConfigStackMC lets you change stack sizes for vanilla items and Fabric mod items from one simple config file.
It works on Paper servers, Fabric singleplayer worlds, and Fabric multiplayer servers. Items you leave out of the config keep their normal stack size.
By default, the included config uses vanilla values, so installing ConfigStackMC does not change gameplay until you edit it.
Demo • Download • Which file? • Configuration • Commands • Troubleshooting
Download the latest build from the Releases page:
https://github.com/TheETR/ConfigStackMC/releases/latest
Each release contains separate files:
| File | Use it for | Where it goes |
|---|---|---|
ConfigStackMC-...-paper.jar |
Paper servers | plugins/ |
ConfigStackMC-...-fabric.jar |
Fabric singleplayer or Fabric multiplayer servers | mods/ |
SHA256SUMS.txt |
Optional checksum verification | Nowhere; only for checking downloads |
You only need the jar that matches your setup. The source code archives are there for developers who want to build the project themselves.
Use the paper jar.
Players do not need to install anything. Only the server needs the plugin.
Use the fabric jar in your local mods/ folder.
Singleplayer does not load Paper plugins, so the Fabric version is the singleplayer option.
Use the fabric jar on the Fabric server.
ConfigStackMC is designed to work on the logical server side. If your server setup allows vanilla or unmodded clients, players should not need ConfigStackMC just for this mod. If your modpack/server already requires Fabric clients for other mods, keep using the matching Fabric setup for that pack.
Each release targets a specific Minecraft version. Check the release title before downloading and use the jar that matches your game or server version.
Example release title:
ConfigStackMC v1.0.0-mc26.1.2
Paper and Fabric builds are provided separately for the same target version.
A successful build means the project compiled for that target. For an important server or world, test the new jar once before replacing your current setup.
- Download the
ConfigStackMC-...-paper.jarfile from Releases. - Put it into your Paper server's
plugins/folder. - Start or restart the server.
- Open the generated config:
plugins/ConfigStackMC/config.yml
- Edit the stack sizes you want.
- Run this command in game or console:
/stackconfig reload
Install Fabric Loader and Fabric API for the Minecraft version shown in the release notes, then download the ConfigStackMC-...-fabric.jar file.
- Put the Fabric jar into your local
mods/folder. - Start the game once.
- Open the generated config:
config/configstackmc.yml
- Edit the stack sizes you want.
- Run:
/stackconfig reload
- Put the same Fabric jar into the server's
mods/folder. - Start or restart the server once.
- Open the generated config:
config/configstackmc.yml
- Edit the stack sizes you want.
- Run:
/stackconfig reload
Paper config path:
plugins/ConfigStackMC/config.yml
Fabric config path:
config/configstackmc.yml
Default config uses normal vanilla values. It is safe to install without changing anything.
max-allowed-stack-size: 99
warn-dangerous-items: true
items:
dried_ghast: 64
bell: 64
ender_pearl: 16
snowball: 16
egg: 16
totem_of_undying: 1
saddle: 1
minecart: 1
water_bucket: 1
lava_bucket: 1
milk_bucket: 1Example edited config:
max-allowed-stack-size: 99
warn-dangerous-items: true
items:
ender_pearl: 64
snowball: 64
egg: 64
totem_of_undying: 16
water_bucket: 16
lava_bucket: 16
milk_bucket: 16Item id rules:
ender_pearlis treated asminecraft:ender_pearl.minecraft:totem_of_undyingalso works.- Items not listed in the config stay completely vanilla.
- Invalid item names are ignored with a warning instead of crashing the server/game.
- Stack sizes must be from
1to the safe API limit, currently99.
On Fabric, modded items should work as long as you use their full item id:
items:
create:brass_ingot: 64
farmersdelight:tomato: 32
another_mod:custom_item: 16The part before : is the mod id. Leaving it out makes ConfigStackMC treat the item as a normal minecraft: item.
Paper does not have true Fabric/Forge mod items. Custom items added by Paper plugins are usually based on a vanilla material, so ConfigStackMC may only see the base item instead of that custom item by itself.
| Command | Permission | What it does |
|---|---|---|
/stackconfig reload |
stackconfig.reload |
Reloads the config and reapplies rules |
/stackconfig info <item> |
stackconfig.info |
Shows configured and vanilla stack size info |
/stacks |
same permissions | Short alias for /stackconfig on Paper |
Examples:
/stackconfig reload
/stackconfig info ender_pearl
/stackconfig info minecraft:totem_of_undying
Important
After using /stackconfig reload or /stacks reload, some existing stacks may not update instantly. Reopen the inventory, reconnect, or restart the server/singleplayer world if needed.
ConfigStackMC only changes the max stack size of configured items.
It does not:
- rename items
- change lore
- add enchantments
- repair or damage items
- merge different items together
- touch items that are not listed in the config
Minecraft still decides whether two item stacks are compatible. For example, two items with different custom data usually will not stack together even if their max stack size is higher.
Be careful when increasing stack sizes for items that can store special data, such as:
- shulker boxes
- bundles
- written books
- filled maps
- damaged tools
- armor
- weapons
ConfigStackMC does not block them, but stacking data-heavy items can have gameplay consequences. Keep warn-dangerous-items: true enabled if you want warnings in the log.
Most problems are caused by using the wrong jar or mixing versions.
- Paper server: use the jar with
paperin its name and place it inplugins/. - Fabric: use the jar with
fabricin its name, place it inmods/, and make sure Fabric Loader and Fabric API match the Minecraft version shown in the release. - Config changes are not showing: run
/stackconfig reload, then reopen the inventory or reconnect. Existing stacks may need a server or world restart. - Still not loading: check the first ConfigStackMC warning or error in the server/game log. It usually points directly to the problem.
Still stuck or found a bug? Open an issue and include your Minecraft version, platform, ConfigStackMC version, and the relevant log or error message.
Most users do not need to build this project. Download a jar from Releases instead.
Default local build:
./gradlew buildBuild for a specific target manually:
./gradlew :common:test :paper:jar :fabric:jar --no-daemon --stacktrace \
-PminecraftVersion=26.1.2 \
-PpaperApiVersion=26.1.2.build.69-stable \
-PpaperApiVersionShort=26.1 \
-PfabricLoaderVersion=0.18.6 \
-PfabricApiVersion=0.152.1+26.1.2Artifacts are separate:
paper/build/libs/ConfigStackMC-1.0.0-paper.jarfabric/build/libs/ConfigStackMC-1.0.0-fabric.jar
The release workflow supports:
- manual releases through Actions > Release > Run workflow
minecraft_version: auto- automatic daily checks for new compatible targets
- release tags like
v1.0.0-mc26.1.2
All rights reserved unless a separate license file says otherwise.
