Rust gather rates & modded servers2x, 5x, 10x - rates, stacks & crafting via plugin

Published on August 4, 2026 · last updated on November 8, 2026

Important: rates run through plugins

Unlike some other games, vanilla Rust has no simple convar like "gather.rate 5". A modded server with increased rates therefore requires a modding framework (Oxide/uMod or Carbon) and suitable plugins. Only then can gather, stack and crafting values be adjusted.

Gather rates

For the actual gather rates, GatherManager is the most widely used plugin. After installing it, you set multipliers in its config - for example for harvesting wood, stone and ore as well as for pickups:

"GatherDispenserModifiers": { "Tree": 2.0, "Ore": 2.0 },
"PickupResourceModifiers": { "*": 2.0 },
"QuarryResourceModifiers": { "*": 2.0 }

That turns vanilla into a 2x server. For 5x or 10x, set the values higher accordingly. Reload the plugin after making changes.

Stack sizes & craft speed

Higher rates go well with bigger stacks and faster crafting:

• StackSizeController - increases the maximum stack size of items so the inventory does not overflow at high rates.
• Craft speed plugins - shorten crafting times (for example "InstantCraft" or configurable multipliers).
• Smelt speed plugins - speed up furnaces and smelting.

Combine the plugins to match the type of server you want - a 10x server without bigger stacks and faster crafting feels unbalanced.

Do not forget balance

Higher rates change the game feel considerably: bases go up faster, PvP starts earlier. State the rates clearly in the server name and description (for example "5x | Instant Craft | Bigger Stacks") so players know what to expect. For vanilla purists, a server without gather plugins stays at Facepunch's original rates.

Which rate fits which server?

The rate is not just a matter of taste - it determines how much time your players have to invest per week to keep up. That is what you should choose it by:

• 1x (vanilla). The game as it was intended. Needs players who can invest several hours at a stretch. Too slow for an after-work session.
• 2x to 3x. The most popular range. The progression curve stays noticeable, but one evening is enough for a visible step forward. The right choice for most community servers.
• 5x to 10x. The focus shifts from gathering to fighting. Bases stand on the first evening, raids start early. Needs an active player base, otherwise everything has been achieved after two days and nobody is left.
• Beyond that. A genre of its own - more arena than survival.

The higher the rate, the shorter the sensible wipe cycle. A 10x server that only wipes monthly is played out after a week. Weekly wipes fit better there - more on that under Force wipe.

What has to be changed together

The most common reason a server feels unbalanced despite increased rates is a half-done adjustment. These four values belong together:

1. Gather rate. How much you get per hit.
2. Stack sizes. At 5x, the inventory fills up five times as fast. Without bigger stacks, players spend the time they saved walking to their box - the gain evaporates.
3. Craft speed. When material is plentiful, the wait while crafting becomes the real bottleneck.
4. Furnace and recycler speed. Otherwise, smelting ore takes longer than gathering it.

What you should not touch, on the other hand, are the decay times of buildings and the raid costs, as long as you do not know exactly what you are doing: both shift the balance between attack and defense more than any gather rate.

Back up and change the configuration

Because the rates run through plugins, they live in the plugins' configuration files - depending on the framework under oxide/config/ or carbon/configs/. Changes there take effect after reloading the plugin, usually without a full server restart.

If possible, only change the rates at a wipe. Raising gather rates in the middle of a running round devalues the work of those who played before - that is the most common reason regulars leave a server. Announce changes and put them into effect with the next wipe.

Back up the configurations first: with us, backups are self-service across the board via WebFTP or SFTP, see Create backups. A plugin configuration that has grown over months is quickly lost and tedious to rebuild.

Frequently asked questions