keepcalculator

06 Numbers and Powers

Increase Item Stack Limits on a Rust Server

Card No. 06·73330 · Updated · Standard formula, shown below

This guide explains how to raise the maximum stack size for items on a Rust server, allowing players to carry more of a single resource or item in one inventory slot. You’ll need access to your server’s files and a text editor; no plugins are required for the basic method.

What You’ll Need

  • Access to your Rust server’s file system (via FTP, a hosting control panel, or a local install).
  • A text editor like Notepad++ or VS Code (plain Notepad works too, but avoid Word).
  • Basic knowledge of editing server configuration files.

Step-by-Step

  1. Locate the server configuration file. The file you need is called server.cfg. It is typically found in the server/ folder of your Rust server directory. If you use a hosting provider, look for a “Config Files” or “Server Settings” section in their control panel.
  2. Back up the current file. Before making any changes, copy server.cfg to a safe location (e.g., server.cfg.backup). This ensures you can revert if something goes wrong.
  3. Open server.cfg in your text editor. Scroll to the bottom of the file. You can add the new settings anywhere, but keeping them at the end makes them easy to find.
  4. Add the stack size command. The command to change stack sizes is server.itemstacksize. For example, to set the maximum stack size to 1000 for all items that support stacking, add this line:
    server.itemstacksize 1000
    This overrides the default (which is usually 10 for most resources, 100 for some like wood, and 1 for items that don’t stack).
  5. Save the file. Save your changes to server.cfg.
  6. Restart the server. For the changes to take effect, you must restart your Rust server. Use your hosting panel’s restart button or stop and start the server process.
  7. Verify the change. Join your server and pick up a stackable item (like wood or stone). The stack size should now be the value you set. If you had items already in your inventory, they may not change until you drop and re-pick them up.

Common Mistakes

  • Editing the wrong file. Some servers have multiple config files (e.g., server.cfg vs serverauto.cfg). Make sure you’re editing the one that is loaded at startup. Check your hosting provider’s documentation if unsure.
  • Using a semicolon or comment incorrectly. In server.cfg, lines starting with // are comments. If you accidentally comment out the line, it won’t work. Also, do not put a semicolon after the value; just a space and the number.
  • Setting an extremely high value. While there’s no hard cap, setting a stack size to 100,000 or more can cause performance issues or UI glitches. Stick to reasonable values like 1000 or 5000.
  • Forgetting to restart. The config is read only at server startup. If you don’t restart, the change won’t apply.

Tips

  • Use a plugin for per-item control. If you want different stack sizes for different items, you’ll need a plugin like Stack Size Controller or Better Stack Sizes. These allow you to set stack sizes per item ID. The server.itemstacksize command applies globally.
  • Test on a staging server. If you’re running a live server, test the new stack size on a separate test server first to ensure it doesn’t break anything.
  • Inform your players. Let your community know about the change so they can adjust their play style. Some players might consider large stacks a quality-of-life improvement, while others might see it as reducing the challenge.
  • Combine with gather rates. If you increase stack sizes, you might also want to adjust gather rates to keep the game balanced. Many server owners use stack size increases alongside higher gather rates for a more casual experience.

Troubleshooting

  • The stack size didn’t change. First, confirm the line is in server.cfg and not commented out. Then, double-check that you restarted the server. If it still doesn’t work, try adding the command to serverauto.cfg (if it exists) instead, as some setups load that file after server.cfg.
  • Items that normally don’t stack now stack. The command applies to all items that have a stackable flag. Some items (like weapons or armor) are hardcoded to not stack, and this command won’t change that. If you see an item stacking that you didn’t expect, it’s likely because it already had a stackable flag but a lower default.
  • Server won’t start after editing. This is rare, but if your server fails to start, check for syntax errors in the config file. Remove any extra spaces or characters. Restore the backup if needed.
  • Stack size resets after a wipe. The server.cfg file persists across wipes, so the setting should remain. If it resets, your hosting provider might be overwriting the file. Check if they have a separate “custom config” option.

Frequently Asked Questions

Does this work on modded servers?

Yes, the server.itemstacksize command works on both vanilla and modded servers. However, if you use a plugin that also modifies stack sizes, the plugin may override the config setting. In that case, configure the plugin instead.

Can I set different stack sizes for different items?

Not with the built-in command. It sets a global maximum for all stackable items. To have per-item control, you need a plugin like Stack Size Controller.

What is the default stack size in Rust?

Most resources (wood, stone, metal fragments) have a default stack size of 10. Some items like wood and stone have a higher default of 100 in certain contexts, but the base is 10 for most. The server.itemstacksize command overrides this.

Will increasing stack sizes affect server performance?

Generally, no. The server stores item counts as integers, so a stack of 1000 uses the same memory as a stack of 10. However, extremely high values (e.g., 1,000,000) might cause UI lag when displaying the number, so keep it reasonable.

Can I set stack size to 0 or a negative number?

No. Setting it to 0 or negative will likely cause errors or make items impossible to pick up. Always use a positive integer.

Does this affect items already in the world?

Items that are already dropped on the ground or in containers will keep their current stack size until they are picked up and re-stacked. Once picked up, they will use the new maximum.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →