How to configure the StackSizeController plugin for Rust
Configure StackSizeController on your Rust server: permissions, every command, worked examples, and the low grade fuel gotcha that affects vehicle spawn fuel.
StackSizeController changes how high items and resources stack in Rust. On a high gather-rate server the vanilla 1,000 wood cap fills a box almost immediately, so raising stack limits is usually one of the first things owners configure.
Before you start
StackSizeController is an Oxide plugin, so your server needs Oxide as its modding framework and the plugin file dropped into oxide/plugins. If you have not set that up yet, start with How to install Oxide.
The plugin writes its config to oxide/config/StackSizeController.json once it has loaded for the first time. You can edit that file directly from the Files tab in your GameServerKings panel, or drive everything through the in-game commands below.
Permissions
Every command is permission-gated, so grant the ones you need before using them. Run these as an admin from the F1 console, or from the Console tab of your Rust game server hosting:
| Permission | Grants access to |
|---|---|
stacksizecontroller.setstack | Set the stack size of a single item |
stacksizecontroller.setstackcat | Set the stack size of a whole category |
stacksizecontroller.setallstacks | Set the stack size of every item at once |
stacksizecontroller.itemsearch | Search items and see their current stack size |
stacksizecontroller.listcategories | List category stack sizes |
stacksizecontroller.listcategoryitems | List the items inside a category |
stacksizecontroller.vd | Regenerate the vanilla stack-size reference file |
Grant them to your admin group like this:
oxide.grant group admin stacksizecontroller.setstack
oxide.grant group admin stacksizecontroller.setstackcat
oxide.grant group admin stacksizecontroller.setallstacks
oxide.grant group admin stacksizecontroller.itemsearch
oxide.grant group admin stacksizecontroller.listcategories
oxide.grant group admin stacksizecontroller.listcategoryitems
oxide.grant group admin stacksizecontroller.vdIf you are new to Oxide groups and permissions, Oxide permissions 101 covers how oxide.grant, groups and users fit together.
Commands
| Command | What it does |
|---|---|
stacksizecontroller.setstack <item> <limit> | Set one item's stack size, by shortname or item ID |
stacksizecontroller.setstackcat <category> <multiplier> | Set stack sizes for an entire category |
stacksizecontroller.setallstacks <multiplier> | Set stack sizes for every item in the game |
stacksizecontroller.itemsearch <name> | Find an item and show its current stack size. Accepts partial names. |
stacksizecontroller.listcategories | List every category and its stack size |
stacksizecontroller.listcategoryitems <category> | List the items in a category. Needs the exact category name. |
stacksizecontroller.vd | Reverts stack sizes and rewrites the plugin's record of every item's vanilla stack size. Run it after a Rust update changes a default. |
Examples
Set wood to stack to 1,000:
stacksizecontroller.setstack wood 1000Set everything in the Resources category:
stacksizecontroller.setstackcat Resources 50000Set every item in the game at once:
stacksizecontroller.setallstacks 20000Not sure of an item's shortname? Search for it first — partial names work:
stacksizecontroller.itemsearch sulfurThings to be careful of
Low grade fuel is tied to vehicle spawn fuel. Rust fuels a vendor-bought minicopter with a fifth of the low grade fuel stack limit, so raising that limit to 10,000 would hand every buyer 2,000 low grade — a large and probably unintended giveaway. The plugin has handled this since v4.1.3: it spots a vendor-spawned minicopter carrying exactly a fifth of a stack and resets it to the vanilla 100. It deliberately stands aside if AirFuel, GetToDaChoppa or VehicleVendorOptions is loaded, because those manage vehicle fuel themselves — so if you run one of them, check what your players actually receive before you raise low grade.
Two more worth knowing:
- Very large stacks affect performance. Huge stacks mean fewer entities for the same loot, which usually helps — but combined with a high gather rate they can make raids and recycling produce enormous single stacks. If your server starts hitching, stack sizes are worth reviewing alongside the usual performance checks.
- Changes apply going forward. Items already sitting in boxes keep their existing stacks until they are moved or combined.
What to read next
- How to install Oxide — getting the modding framework in place
- Oxide permissions 101 — groups, users and
oxide.grant - Popular Rust plugins — what else is worth running
- Rust admin commands — the wider admin reference
Need a Rust server?
Deploy an instantly-provisioned Rust server on high-clock hardware — DDoS protected, no contracts, cancel anytime.
From $13.00 /month