What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The best Rust 2x setup is not one magic number. It is a clearly defined policy: set every intended gather category to 2.0, decide separately whether loot is doubled, keep core server variables in server.cfg, and list the server as Modded when gameplay-changing plugins are active. This prevents a server advertised as 2x from quietly doubling only ore nodes while barrels, pickups, quarries, or loot remain unchanged.
The preset below is a practical starting point for a general Rust server. It uses UGather for category-level gathering controls and Better Loot only if you want a separate 2x loot promise. The numbers are a server-owner choice rather than an official universal standard, so publish the exact scope with every wipe announcement.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Rust Key Cards, Rust Red Key Card, Cobalt Restricted Access Cards, Rust Gift For Gamers, Blue Key... | $25.00 | Buy on Amazon |
| 2 |
|
Rust Video Game Notebook | $15.00 | Buy on Amazon |
| 3 |
|
Rust Game Props Large Furnace (S) | $14.99 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
For a hosted Rust server, Godlike.Host provides a Pterodactyl-based game panel with SFTP/FTP access, a built-in mod installer and updater, and up to three free backups a day with restore. See Godlike.Host Rust servers for current plans.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →What 2x means in Rust
In Rust, 2x normally describes how quickly players acquire resources, but the phrase is ambiguous unless you name the systems included. UGather documents the scale directly: 0.5 is 50% of normal, 1.0 is normal, 1.5 is 150%, and 2.0 is double gather.
#1 Best Overall
- Inspired by the Rust Video Game – These cards replicate the iconic keycards found in Rust (Red, Blue, Green).
- High Quality PVC Plastic – Printed on both sides, durable and water-resistant. Not a sticker.
- Great Rust Gift Idea – Perfect for fans of Rust, whether for cosplay, loot-themed gifts, or collection.
- Wallet-Size Replica – Standard 3.375x2.125 inches, 30 mil thick—fits in any wallet.
- NOT a sticker*
Gathering is broader than striking an ore node. A complete policy can include barrels, bonus resources, resource dispensers, the Giant Excavator, natural pickups, quarries, and survey charges. Crops and other pickup systems may also be governed by the selected plugin or by separate server settings. If only one category is changed, describe the server as 2x for that category rather than as a full 2x experience.
Loot is a different system. A gather multiplier does not automatically change the contents of crates, barrels, or other container tables. Better Loot exposes a global Loot Multiplier, a separate Scrap Multiplier, per-table loot configuration, and separate gather-rate data files. Therefore, a server can be 2x gather with normal loot, or 2x gather and 2x loot; both are legitimate when labeled accurately.
The four decisions to make first
- Scope: gather only, gather plus pickups, or gather plus loot.
- Consistency: whether every relevant category receives the same multiplier.
- Progression: how quickly a solo player or team reaches better weapons, workbenches, and a durable base.
- Maintenance: whether the plugin remains compatible after Rust updates and whether another plugin can override its values.
Three useful 2x server profiles
Choose one profile before editing files. The first is the safest default for a broad audience; the other two make different progression promises.
| Profile | Gather categories | Loot multiplier | Best for | How to describe it |
|---|---|---|---|---|
| 2x gather | All selected UGather categories at 2.0 |
1.0 |
Players who want faster building without accelerated crate progression | 2x gather, normal loot |
| Full 2x progression | All selected UGather categories at 2.0 |
2.0; set scrap separately if promised |
Fast wipes, casual groups, and servers where every major acquisition path is intended to be twice as fast | 2x gather and 2x loot |
| Controlled 2x | Core resource categories at 2.0; exceptional systems chosen deliberately |
1.0 or a documented value |
Owners who want quicker building while preserving scarcity in quarries, excavator output, or rare progression | 2x resources; selected systems unchanged |
For most general servers, the first profile is the clearest starting point. The second is appropriate only when you are comfortable with players reaching tiered weapons and large bases substantially earlier. The third can work well, but every exception must be stated; otherwise players will interpret inconsistent rates as a broken configuration.
A complete gather matrix
If you advertise a full 2x gather server, use one explicit value for every category you intend to expose. The following matrix applies the documented UGather scale consistently.
| Category | Recommended value for full 2x | What to verify in testing |
|---|---|---|
| Barrels | 2.0 |
Break several barrel types in more than one monument and compare the item yield with a normal-rate reference. |
| Bonus resources | 2.0 |
Check bonus drops separately from the main resource yield so a second multiplier is not applied. |
| Resource dispensers | 2.0 |
Test wood, stone, metal, and sulfur nodes, including different tool types. |
| Giant Excavator | 2.0 |
Run a complete production cycle and record the output rather than sampling a partial cycle. |
| Natural pickups | 2.0 |
Collect the same kind of ground pickup repeatedly; do not infer pickup rates from node yields. |
| Quarries | 2.0 |
Measure a full operating interval and confirm that fuel consumption has not been changed unintentionally. |
| Survey charges | 2.0 |
Compare the resources created by several charges because one sample can be unusually lucky. |
| Crops and other pickup systems | 2.0 when the installed configuration exposes the category |
Harvest a complete growth cycle and inspect whether the category is controlled by UGather or another plugin. |
The table is a policy, not a guarantee that every Rust release exposes identical hooks. If a category is not available in your plugin version, say so in the server description instead of silently calling the server full 2x.
How to implement the settings
1. Write the policy before touching the server
Put the intended scope in a short operations note: the gather categories that will be doubled, whether loot and scrap will be doubled, and which systems remain normal. This note becomes the source for your server description, wipe announcement, and post-update checks. It also prevents staff from changing one value during a wipe without updating the public promise.
Recommended Free Tools
2. Keep core variables in server.cfg
Facepunch documents the identity configuration file at server/<identity>/cfg/server.cfg. Create the file if it does not exist, keep related core variables together, and follow the syntax used by the current Rust server guide. Use it for server identity, ports, RCON setup, and other core variables that belong to the server rather than to a plugin.
Rank #2
After editing the file, stop and start the server so every variable is loaded from a clean boot. A restart also makes it easier to distinguish a core configuration problem from a plugin configuration problem. If your host provides a control panel, its file editor may display the same path beneath the server identity; the labels differ by host, but the Rust path remains the reference.
3. Install a plugin framework only when category controls are needed
Vanilla configuration is sufficient for core server variables, but category-level gather and loot controls require a maintained plugin. Install Oxide/uMod according to its current server-owner documentation, then confirm that the framework starts cleanly before adding gameplay plugins. Keep a backup of the configuration and data directories before each Rust update.
4. Configure UGather
- Install the current UGather build compatible with your Rust and Oxide/uMod versions.
- Open the generated UGather configuration or data files using the framework’s normal configuration path.
- Set each category in your written policy to
2.0. For a full preset, that means barrels, bonus resources, resource dispensers, Giant Excavator, natural pickups, quarries, and survey charges, plus crops or another exposed pickup category. - Reload the plugin using the framework’s documented reload method, or restart the server if the configuration requires a full restart.
- Record the final values and plugin version in your administration notes.
Do not install two plugins that both claim to control the same gather event unless you understand their order of operation. If a second gather plugin is active, it may multiply, replace, or undo UGather’s values.
5. Add Better Loot only for a loot promise
Install Better Loot when you need container-level control. Set its global Loot Multiplier to 2.0 only for a server advertised with 2x loot. Set the Scrap Multiplier separately; a 2x loot setting does not by itself prove that scrap is doubled. Review each per-table configuration so a custom crate or barrel table does not contradict the global promise.
If your server is gather-only, leave loot at its normal value and say so. This distinction matters because players often use barrels and crates to obtain weapons, components, and scrap; doubling nodes while leaving those tables normal creates a different progression curve from doubling both systems.
6. Restart, test, and publish the exact values
- Restart the server after the final configuration is saved.
- Use a controlled test account or administrator session to check at least one example from every enabled category.
- Repeat a test after a fresh plugin reload to catch values that are reset or overwritten during initialization.
- Check the console and plugin logs for load errors, missing configuration keys, or version warnings.
- Write the actual values, including loot and scrap, in the wipe announcement and server description.
Loot settings: decide what 2x actually promises
Loot is where many otherwise well-configured servers become misleading. Better Loot’s controls are independent enough that you should treat them as a separate design document.
| Public promise | Global loot multiplier | Scrap multiplier | Required checks |
|---|---|---|---|
| 2x gather, normal loot | 1.0 |
1.0 |
Verify that no per-table override doubles containers. |
| 2x gather and 2x loot | 2.0 |
2.0 if scrap is included in the promise |
Inspect global and per-table settings, then test barrels, crates, and a high-tier table. |
| 2x gather, boosted scrap only | 1.0 |
2.0 |
State that item loot remains normal and scrap is the only boosted container resource. |
Per-table settings can make two containers behave differently even when the global multiplier is correct. Keep custom tables documented, especially after a wipe or plugin update. A player should be able to read your announcement and predict whether a barrel run, quarry, or crate route is being accelerated.
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 matchWhy the server belongs in Modded
Facepunch’s community-server guidance says: “Any plugin that affects a player’s gameplay in any way.” Its examples include changes to gather rates, item spawns, player spawns, and smelting mechanics. uMod’s server-section guidance likewise places gameplay-changing modifications such as gather-rate changes and Gather Manager in the Modded category.
Rank #3
- Acrylic Painting Pla Plastic
A 2x server using UGather or Better Loot therefore belongs in Modded. Changing the listing to Community does not make the gameplay change compliant. Use the listing category that describes the actual server, and mention the active plugins in the description when the listing interface allows it.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Testing checklist before a wipe
Run these checks on a staging instance or during a maintenance window. The goal is not to prove a theoretical multiplier with one lucky drop; it is to find category gaps and conflicts.
- Node test: gather several wood, stone, metal, and sulfur nodes with the same tool and compare total output.
- Barrel test: break enough barrels to reveal whether both item quantity and item selection are being changed.
- Pickup test: collect repeated natural pickups and harvest a crop cycle if crops are included.
- Industrial test: observe a quarry and a Giant Excavator cycle rather than sampling a few seconds.
- Survey test: detonate multiple survey charges and record the resulting resource piles.
- Loot test: open several container types and check both normal items and scrap.
- Conflict test: temporarily disable other gather, loot, economy, or event plugins and repeat one sample from each category.
- Restart test: reboot the server and verify that values persist.
Symptoms and fixes
- Nodes are 2x but barrels are normal: the policy covers only resource dispensers. Enable the barrel category or describe the server as node-focused.
- Loot is unchanged after setting gather to 2.0: this is expected; configure Better Loot separately if the public promise includes containers.
- Values revert after restart: check that the edited file is the active server identity’s configuration and that the framework can write its data files.
- Output is higher than 2x: look for a second gather plugin, a bonus-resource multiplier, or a per-table override.
- One category fails after a Rust update: review plugin load warnings, install a compatible release, and temporarily state that category as normal until it is verified.
- Players report inconsistent rates: compare the exact category named in the report; barrels, pickups, quarries, and nodes are separate systems.
How 2x changes progression
Doubling resource acquisition shortens the time needed to place a starter base, replace tools, and stockpile building materials. If loot is doubled as well, weapon, component, and scrap progression accelerates independently. That combination can move solo players and small teams through workbench tiers quickly, while larger groups may reach endgame stockpiles early in the wipe.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Use the controlled profile when you want faster construction but still want monument routes and crate runs to matter. Use full 2x progression when the server’s identity is speed and convenience. Neither is objectively best; the correct choice depends on wipe length, expected team size, and whether your community values building access or a slower technology race.
Solo and team considerations
- Solo-focused servers: full 2x can reduce the time burden of farming and make upkeep manageable without a large group.
- Small-team servers: 2x gather with normal loot often preserves meaningful monument decisions while removing the most repetitive resource grind.
- Large-group servers: doubling every source can create very large stockpiles, so consider normal loot or a controlled exception for industrial systems.
What to write in the wipe announcement
Use plain language and list exceptions. A precise announcement could say:
New wipe: 2x gather on barrels, bonus resources, resource dispensers, Giant Excavator, natural pickups, quarries, survey charges, and supported crop pickups. Loot and scrap remain at normal rates. Gameplay-changing plugins are active, so the server is listed as Modded.
If you choose full progression, replace the final rate sentence with a direct statement that the global loot and scrap multipliers are both 2.0. Do not call the server simply 2x when one of those systems is intentionally normal.
Maintenance after Rust updates
Rust updates can change plugin hooks, configuration keys, or the behavior of a category. Before updating a live server, back up server.cfg, plugin configuration, plugin data, and any custom loot tables. Read the plugin’s compatibility notes, update Oxide/uMod when required, and test on a copy before reopening the server.
After every update, repeat at least one test for each promised category, check the console for load errors, and confirm the listing still says Modded. Keep a dated change log containing plugin versions and multiplier values. This makes it possible to identify whether a reported rate change came from a Rust update, a plugin update, or an administrative edit.
Recommended baseline
For a dependable general-purpose server, set all UGather categories that you advertise to 2.0, leave Better Loot at normal rates unless you explicitly want 2x loot, and publish the full scope in the wipe message. Store core variables in server/<identity>/cfg/server.cfg, use a maintained plugin only where category controls are necessary, test after every restart and Rust update, and list the modified server as Modded. This approach gives players a predictable progression curve instead of an unexplained collection of boosted numbers.
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.
