Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsTo increase item stack limits, install the Oxide/uMod mod framework and the StackSizeController plugin. Vanilla Rust does not provide a supported server.cfg setting for stack sizes. After the plugin has generated its configuration, change the multipliers in oxide/config/StackSizeController.json (or use its console commands), then reload the plugin with oxide.reload StackSizeController.
Playing with friends? Godlike.Host runs hosted Rust servers from 10 data-center locations, with free DDoS protection.
This method can apply one multiplier globally, different multipliers by category, and individual item settings, depending on the options exposed in the generated configuration. The plugin documentation lists 2,147,483,647 as the maximum stack size, describing it as a hardcoded Rust limit.
As an Amazon Associate I earn from qualifying purchases.
Free tools Windows power users keep installed
One-click scans. No signup required.
Why server.cfg cannot change Rust stack sizes
Rust’s vanilla stack limits are hardcoded rather than exposed as ordinary server configuration variables. Adding a guessed setting to server.cfg will not change how many units an item can hold. A server can still use server.cfg for the settings that Rust exposes there, but stack-size overrides require a mod framework and a plugin that changes the limits at runtime.
The practical route documented for this task is:
- Install Oxide, also known as uMod, on the Rust server.
- Download the community StackSizeController plugin and place its plugin file in
oxide/plugins. - Start the server once so the plugin can create its configuration.
- Edit
oxide/config/StackSizeController.json, or issue the plugin’s console commands. - Reload the plugin with
oxide.reload StackSizeController.
StackSizeController is listed on uMod as a community plugin by AnExiledDev. It is not a built-in Facepunch server option, so updates to Rust or Oxide can affect compatibility. The available material does not establish a current plugin version or a guaranteed Oxide/Rust compatibility date; check the plugin’s current listing and your server’s own startup log before changing a production server.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Before changing anything
Confirm that you control the server files or console
You need either shell/file access to the server or an administrative console that accepts Oxide commands. A game client alone cannot change server-wide stack limits. If a hosting control panel hides the file system, use its file manager or ask the host to install Oxide and provide access to the Oxide configuration directory.
Back up the configuration
Stop the server, or use the host’s safe file-editing method, and make a copy of oxide/config/StackSizeController.json before changing it. Keep the original name plus a date or another clear identifier. A backup gives you a known-good way back if a typo prevents the plugin from loading or if a later update changes the configuration format.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchDecide what “2x” or “5x” means for your server
The plugin uses multipliers. Enter a plain number such as 2 or 5, not 2x or 5x. A multiplier of 2 requests twice the normal limit, while 5 requests five times the normal limit, subject to the item’s own Rust limit and the plugin’s behavior.
Plan exceptions before editing. Some vanilla categories intentionally have small limits. Raising every item to the same value can make medical items, ammunition, components, food, or other high-impact resources behave very differently from the rest of the server. A global multiplier followed by category or item exceptions is usually easier to reason about than assigning a separate value to every item from the start.
Install Oxide and StackSizeController
1. Install Oxide/uMod
Install the Oxide/uMod build intended for your Rust server through your host’s supported deployment process. When installation is complete, the server should contain an oxide directory alongside the Rust server files. The exact installer and restart sequence varies by host, so use the host’s current instructions rather than copying an old command from an unrelated server version.
Start the server once after installing Oxide. Watch the startup console for Oxide loading messages and errors. If the oxide directory is not created, or the log reports that Oxide failed to load, fix that problem before installing StackSizeController; the plugin cannot work without the framework.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
2. Put the plugin in the plugins directory
Download the StackSizeController plugin from its uMod listing and place the plugin file in:
oxide/pluginsDo not put the file in oxide/config or oxide/data. The plugins directory is where Oxide discovers plugin files. After copying it, restart the server or reload the plugin through the administrative console. A successful load should create the configuration file at:
oxide/config/StackSizeController.jsonIf no configuration appears, check the startup log for a filename error, a missing dependency, a malformed plugin file, or an Oxide/Rust compatibility problem. Do not create a random JSON structure in a different directory; the plugin’s generated file is the authoritative template for the version you installed.
Configure stack multipliers in StackSizeController.json
Use the generated file as the schema
Open oxide/config/StackSizeController.json in a text editor that preserves plain UTF-8 text. The configuration holds global settings, category settings, and per-item settings. Names and nesting can change between plugin releases, so retain the keys generated by your installed version and alter only their values.
Set multipliers as numbers:
1leaves a limit at its normal value.2requests a two-times limit.5requests a five-times limit.
Do not append an “x,” put the number in quotation marks, or replace a JSON number with a comment. JSON does not accept comments, and malformed punctuation can stop the plugin from loading. Keep commas between properties, keep braces and brackets balanced, and preserve the capitalization of existing item or category keys.
Set a global multiplier
Use the global setting when the goal is a simple server-wide rule, such as making ordinary storage more generous across the entire game. Change the global multiplier in the generated configuration to the desired plain number. A global setting is easy to audit, but it also affects every category unless a more specific category or item setting overrides it.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Override a category
Use the category section for deliberate exceptions. For example, you can keep the global value at one level and assign a lower or higher multiplier to a category whose vanilla limits are intentionally small. The available category names are the ones shown in your generated file; copy them exactly instead of guessing spelling or capitalization.
Override an individual item
The per-item section is the most precise option. Use it when one item needs a different limit from the rest of its category. Copy the item identifier exactly as the plugin presents it. An item-specific value should be treated as the narrowest rule, but confirm the result in-game because precedence can depend on the plugin release.
Recommended Free Tools
Save and validate the JSON
Save the file, then validate its JSON syntax before reloading. A missing comma, an extra comma at the end of an object, or an unmatched brace is enough to make the configuration unreadable. If your editor has no JSON validator, compare the edited file carefully with the backup and change one setting at a time. Avoid editing files under oxide/data; the documented stack-size configuration belongs under oxide/config.
Apply changes with the plugin reload command
After saving the file, run:
oxide.reload StackSizeControllerUse the server console or an administrative console with permission to execute Oxide commands. Watch the response and the server log. A successful reload should not produce a JSON parse error or a plugin exception. If the reload fails, restore the backup, reload again, and then make smaller changes.
A full server restart is useful after a major change or framework update, but it is not a substitute for correcting an invalid configuration. Reloading applies the plugin’s current settings without requiring players to reconnect solely because you changed a multiplier.
Use console commands instead of editing the file
The plugin listing and hosting guides cite two commands:
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
stacksizecontroller.setallstacks 2stacksizecontroller.setstackcat <category name> <multiplier>
The first targets all stack categories with the supplied multiplier. The second targets one category. Replace the category-name and multiplier placeholders with values accepted by the categories in your installation. Enter a number such as 2, not 2x.
These commands are convenient when you have console access but do not want to open a server file. The cited command examples come from a single documentation snippet and were not independently verified on a live server, so treat the console response and the resulting configuration as the authority for your version.
Check whether a command persisted
After running a command, inspect oxide/config/StackSizeController.json. Then restart the server and inspect the file again. File edits are intended to persist across restarts. Persistence for command-made changes should be checked on your server rather than assumed, because the available documentation does not verify whether every command writes the changed value back to the configuration.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Config file or console command?
| Method | Persistence | Control | Access required | Main risk |
|---|---|---|---|---|
StackSizeController.json |
Configuration edits persist across restarts when the file remains valid. | Global, category, and per-item settings are available through the generated configuration. | Shell, file-transfer, or control-panel file access. | A JSON typo can prevent the plugin from loading until the file is repaired or restored. |
stacksizecontroller.setallstacks |
Check the configuration after a restart; persistence is not established by the cited documentation. | One multiplier for all categories. | Administrative server console. | A broad change can unintentionally alter every item and may not be written back as expected. |
stacksizecontroller.setstackcat |
Check the configuration after a restart; persistence is not established by the cited documentation. | One category at a time. | Administrative server console. | The category name must match the plugin’s accepted name exactly. |
For a repeatable production setup, the configuration file is the easier source of truth. Console commands are useful for quick tests, temporary events, or administrators who have console access but no file access. Record any temporary command-based change so another administrator knows what to verify after a restart.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Verify the new limits in-game
Test an ordinary item
Join with an account that can access the relevant inventory, place enough of one item into a stack, and confirm the displayed maximum. Test a new stack as well as an existing stack; an old stack may retain its previous quantity until the game or plugin handles it again.
Test an exception
If you configured a category or item override, test that item separately from an item governed only by the global multiplier. This confirms that the specific rule is being read and that the category or item identifier was copied correctly.
Test a restart
Restart the server during a maintenance window, then repeat the inventory test. This catches two common operational mistakes: a command that did not persist and a file edit that was overwritten, rejected, or saved in the wrong location.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Check logs when the number is not what you expected
Review the Oxide and server console immediately after loading or reloading the plugin. Look for configuration parse errors, unknown category or item names, plugin exceptions, and messages indicating that a value was clamped. Keep the exact multiplier, the affected item, and the time of the test in your administration notes so you can reproduce the result after an update.
Limits, edge cases, and safe operating choices
The documented maximum is an integer limit
StackSizeController’s documentation lists 2,147,483,647 as the maximum stack size and describes it as a hardcoded Rust limitation. This is a ceiling, not a recommendation. Very large stacks can make storage, loot distribution, crafting balance, and inventory management difficult to reason about. Choose a value that serves your server’s rules instead of moving every item close to the ceiling.
Small vanilla stacks may be intentional
Some vanilla categories deliberately use small limits. A global multiplier changes those categories too unless you add a more specific rule. If your server’s aim is faster building but normal combat balance, apply a broad value only where it fits and use category or per-item settings for the exceptions.
Do not confuse a multiplier with a fixed quantity
The setting expresses a multiplier relative to the normal limit. It does not mean “set every stack to exactly 2” or “set every stack to exactly 5.” Items with different vanilla limits will therefore end up with different absolute quantities when they share the same multiplier.
Compatibility is not guaranteed indefinitely
Rust, Oxide/uMod, and community plugins are updated independently. The available documentation does not establish a current StackSizeController release number or a tested compatibility window. Before applying a Rust update to a busy server, back up the configuration, review the plugin’s current uMod entry, restart on a test instance if possible, and inspect the logs for load errors.
Troubleshooting checklist
The server still uses vanilla limits
- Confirm that Oxide/uMod loaded successfully, not merely that its directory exists.
- Confirm the plugin file is in
oxide/plugins, not inoxide/configoroxide/data. - Confirm that
oxide/config/StackSizeController.jsonwas generated by the plugin you installed. - Reload with
oxide.reload StackSizeControllerand read the response and log. - Check that the multiplier is a plain number, such as
2, rather than text such as2x.
The plugin refuses to reload
- Restore the backup configuration and reload to determine whether the edit introduced the problem.
- Validate commas, braces, brackets, and quotation marks in the JSON.
- Remove comments or trailing commas, which are not valid JSON.
- Make sure you edited the file under
oxide/config, not a similarly named file underoxide/data. - Read the startup log for a plugin exception or an Oxide/Rust compatibility error before trying another value.
A category command has no visible effect
- Use the category name exactly as shown in the generated configuration.
- Confirm that the command was entered in an administrative server console rather than ordinary chat.
- Test an item that belongs to that category and compare it with an item controlled by the global setting.
- Inspect the JSON and restart to determine whether the command changed a persistent value.
One item ignores the global value
Look for a category or per-item override. More specific settings may intentionally replace the global value. Temporarily set the relevant specific rule to 1 or remove it according to the generated configuration’s structure, reload, and test again. Always keep the original file so you can restore an established configuration.
A practical rollout plan
- Copy the existing
StackSizeController.jsonand record the Rust and Oxide versions shown by the server. - Choose a modest global multiplier and list the categories or items that must remain different.
- Change only the global value, reload, and test several inventories.
- Add category overrides one at a time, reloading and testing after each change.
- Add per-item overrides only when a category rule is too broad.
- Restart the server and repeat the tests to verify persistence.
- Publish the final values in your server rules so players know whether a stack is intentionally larger rather than assuming a bug.
This staged approach makes it clear which setting caused a problem and avoids turning a single typo or overly broad multiplier into a server-wide balancing issue.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
