/// SUPPORTED THIRD-PARTY PLUGIN
Stack Size Controller
Free guide for configuring this third-party plugin in the Hub. To install it, use its plugin page or official source.
Prepare your file
- Check the installed version
This guide describes Stack Size Controller 4.1.3. Use the same version in the configurator.
- Get the settings
Click Import, then From my server. Select the files and confirm loading them. Selecting a server does not replace the open document. You can also import files from this device or a configuration from My projects.
- Edit and send
Adjust settings, fix errors, then use Send to transfer files to the selected server. A conflict blocks sending until you choose how to resolve it. You can still export only the files you need.
Server transfers have private backups. Save keeps your work in My projects; it does not send anything to the server. A download also lets you resume without a server connection.
Settings for this version
General 7
- Restore vanilla stacks on unload
- On / off · required
Restores vanilla stack sizes when the plugin unloads.
JSON path
RevertStackSizesToVanillaOnUnload - Stack full-durability items
- On / off · required
Allows full-durability weapons and other durable items to stack.
JSON path
AllowStackingItemsWithDurability - Hide plugin-name prefix
- On / off · required
Remove the [StackSizeController] prefix from replies sent to players. This setting works in the 4.1.3 source; it does not change stack sizes.
JSON path
HidePrefixWithPluginNameInMessages - Global stack multiplier
- Number · required
Multiply base stack sizes without an individual multiplier or a category multiplier greater than 1. Those more specific settings replace the global multiplier rather than multiply with it.
JSON path
GlobalStackMultiplier - Category multipliers
- JSON value · required
Enlarge a category’s stacks when its value is greater than 1, unless an individual multiplier exists. A value of 1 or less lets the global multiplier apply; the two do not combine.
JSON path
CategoryStackMultipliers - Per-item multipliers
- JSON value · required
Multiply an item’s base stack size and replace its category and global multipliers. A short-name key wins over a numeric-ID key. The base comes from IndividualItemStackSize when present.
JSON path
IndividualItemStackMultipliers - Per-item stack sizes
- JSON value · required
Define base stack sizes by item short name. The selected individual, category or global multiplier still applies, so this is not always the final limit. The plugin populates this list on load.
JSON path
IndividualItemStackSize
Configuration version 3
- Major version
- Choice · required
Internal configuration format marker. Keep the value supplied for this plugin version.
JSON path
VersionNumber → MajorAllowed values: 4
- Minor version
- Choice · required
Internal configuration format marker. Keep the value supplied for this plugin version.
JSON path
VersionNumber → MinorAllowed values: 1
- Patch version
- Choice · required
Internal configuration format marker. Keep the value supplied for this plugin version.
JSON path
VersionNumber → PatchAllowed values: 3
Plugin instructions
Stack Size Controller 4.1.3
Configure Stack Size Controller for free under Oxide using oxide/config/StackSizeController.json. This guide covers the official uMod version 4.1.3 observed on 2026-08-02, under the MIT license. With an SFTP-connected server, use Install on its product page to retrieve the plugin from uMod. Otherwise, download it from its official source.
Use global, category and per-item rules to adjust Rust stacks. Reviewed on 2026-10-05 against AnExiledDev’s official guide, the pinned 4.1.3 source (patched by chrome), schema and defaults. The Hub edits JSON, not live item definitions or inventory.
Fixed settings
RevertStackSizesToVanillaOnUnloadrestores vanilla sizes when the plugin unloads.AllowStackingItemsWithDurabilitypermits full-durability items to stack.HidePrefixWithPluginNameInMessagesremains in the file, but currently has no effect according to the official documentation.GlobalStackMultiplieris the fallback when no individual multiplier or category multiplier above 1 applies.VersionNumberis managed by the plugin and is4.1.3in the supplied default configuration.
Categories and items
CategoryStackMultipliersstarts with the Rust categories known to version 4.1.3. The plugin creates these entries from the game’s categories while running on the server. The configurator also preserves any additional numeric category entries.IndividualItemStackMultipliersmaps an item short name or numeric item ID to a numeric multiplier. Individual values take priority over category values.IndividualItemStackSizeassociates item short names with integer base stack sizes, which can still be multiplied. This list is empty in the initial configuration; after first load, the plugin fills it from current Rust item definitions and updates it when new items appear. The supplied example therefore leaves this list empty.
The Rust hard limit for a stack is 2,147,483,647. After editing, reload StackSizeController so configured sizes are applied.
Official source: https://umod.org/plugins/stack-size-controller
Recipe: double resource stacks only
- Set
GlobalStackMultiplierto1andCategoryStackMultipliers > Resourcesto2; keep other categories at1. - Check
IndividualItemStackMultipliersfor resource overrides, which take priority over the category. - Export, reload
StackSizeControllerand verify wood and stone on a test server.
In 4.1.3, a category multiplier applies only when greater than 1; otherwise global is the fallback. Individual, category and global multipliers do not multiply together.
Recipe: keep wood at 1,000 per stack
- Set
IndividualItemStackSize > woodto1000. - Set
IndividualItemStackMultipliers > woodto1to prevent global/category increases from multiplying this base. - Reload and check a fresh wood stack. Keep
RevertStackSizesToVanillaOnUnloadtrue if unloading should restore vanilla sizes.
Permissions and limits
The in-game commands have matching permissions: stacksizecontroller.setstack, stacksizecontroller.setstackcat, stacksizecontroller.setallstacks and stacksizecontroller.itemsearch. Grant editing commands only to trusted staff. Exporting does not grant them or apply JSON to the server.
Ignored items and durability handling can bypass increases. Set individual base sizes to at least 1: some runtime paths read those values directly, so do not rely on a later clamp to repair zero. The configurator blocks zero before export and starts new entries at 1. Avoid extreme multipliers and leave VersionNumber plugin-managed.
Questions
Why is my per-item size still multiplied?
The per-item size is a base, not a final cap. The source then tries an individual multiplier by shortname, then numeric ID, then a category value above 1, then global. To preserve a fixed base, use an individual multiplier of 1.
Why is the default item list empty?
The server creates it from Rust definitions on first load and adds newly introduced items later. Import your server-generated JSON to retain the actual list; the initial example cannot predict future items.
Install the files
With a connected server, click Send in the configurator. The result shows whether the files were sent and the plugin reloaded. Without RCON, reload the plugin from your server panel after sending.
Without a connected server: Keep a copy of the current files. Place each export in the folder shown before export, or follow the paths in the ZIP. Do not put data or translation files in the config folder.
Follow the plugin instructions above for dependencies and reloading. Exporting does not connect the site to your server.