Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

On a Rust server, loot is normally changed with a server plugin rather than by editing a vanilla game file. On Oxide/uMod, the most common approach is Better Loot: edit its global configuration in oxide/config/BetterLoot.json and its per-container data in oxide/data/BetterLoot/LootTables.json. MagicLoot, an in-game Loot Table & Stacksize GUI, and Raidable Bases use different files and commands. Back up the relevant folders, check the plugin version, validate JSON, then reload only the plugin you changed.

What controls loot on a Rust server?

Rust’s default loot is part of the game’s server-side systems, but administrators generally do not customize it by opening a Facepunch game file. Custom tables, multipliers, blacklists, stack sizes and event-specific rewards are supplied by plugins running on an Oxide/uMod or Carbon framework.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

The framework matters because it determines where configuration and data are stored and which reload command is available. A plugin may also keep global settings separate from generated or per-container tables. Editing the wrong file can appear to do nothing, or can cause a plugin to regenerate its defaults.

  • Oxide/uMod: commonly stores settings under oxide/config/ and plugin data under oxide/data/.
  • Carbon: is designed to run most Oxide plugins through a compatible hook API, but Carbon-specific paths and commands must be checked against the installed plugin and framework version.
  • Do not install both frameworks on the same server: compatibility descriptions say Carbon can run many Oxide plugins, while community reports warn against running Carbon and Oxide together. Treat them as alternatives and follow the framework’s installation guidance.

Before changing anything, identify the framework, the exact plugin name and version, and whether the server is a production server or a disposable test instance.

#1 Best Overall
Sale
Compressed Air Duster,130000RPM Super Power Cordless Air Duster,Rechargeable Brushless Blower,3 Gear Adjustable Blower with LED Light,Dust Remover for Computer/House/Outdoor/Car
  • Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
  • With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
  • Wide Application:Upgraded attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
  • Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
  • Warranty & Support: Our Electric air duster comes with 5 years warranty and 24/7 customer service. During this period, if you have any questions,pls kindly feel free to contact us.

Choose the method that matches your goal

Method Best for Main files or command Important requirement
Better Loot Global loot behavior plus separate tables for container prefabs oxide/config/BetterLoot.json; oxide/data/BetterLoot/LootTables.json File names and fields can vary by plugin release; confirm the installed version.
MagicLoot Container multipliers, blacklists, per-container rules and stack-size changes oxide/config/MagicLoot.json; oxide/data/MagicLoot.json Keep configuration settings and stack-size data in their respective files.
Loot Table & Stacksize GUI Administrators who prefer editing tables in game In-game GUI On Carbon, enable Harmony references with c.harmonyreference 1; on Oxide, install Image Library.
Raidable Bases Loot inside Raidable Bases events oxide/data/RaidableBases/ or, on Carbon, carbon/data/RaidableBases/ Default_Loot.json is the fallback; rb.populate all generates an editable list.

These methods are not interchangeable. Changing Better Loot does not automatically rewrite Raidable Bases event loot, and changing a MagicLoot stack-size file does not replace a Better Loot table.

Prepare the server before editing

1. Make a recoverable backup

Copy the entire oxide/ directory, or the corresponding carbon/ directory, before touching a configuration or data file. At minimum, preserve the plugin’s configuration and data subdirectories. Give each backup a date and keep the last known-good copy outside the live server folder so a plugin cannot overwrite it.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

2. Confirm the installed plugin release

Open the plugin’s current documentation or release page and compare its version with the file on your server. Field names, defaults and file names are not guaranteed to remain stable. Better Loot is a notable example: version 4 is not compatible with old loot-table files. The plugin page describes a converter at looty.cc/converter; use it only after checking that the converter matches your installed release and keep the original files as a backup.

3. Decide whether to stop or unload the plugin

A cautious workflow is to stop the server or unload the individual plugin before hand-editing its data. Community reports say a loaded plugin may save its in-memory copy over manual changes, but this behavior is not established as a universal rule for every release. If you cannot stop the server, use the plugin’s documented save or reload procedure and make a backup immediately before editing.

4. Use a JSON-aware editor and validator

These files are JSON, so property names and capitalization matter. Keep quotation marks around strings, use commas between properties, and do not leave a trailing comma after the final property. Run the completed file through a JSON linter before reloading. A single missing brace or comma can prevent the plugin from loading and may be reported only in the server console.

Rank #2
EVEO® Screen Cleaner Spray Kit (Streak-Free) TV Screen Cleaner for Smart TV, Lcd, LEd, Oled | Computer Screen Cleaner Spray and Wipe Microfiber Cloth - TV, Monitor, Laptop, iPad, Car - 6.7oz 1 Pack
  • Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
  • Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
  • Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
  • Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
  • Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth

5. Test on a separate instance when possible

Use a test server with the same Rust build, framework, plugin versions and configuration. Test one change at a time, record the original file, and inspect the console after reload. This isolates a bad field or a missing dependency from unrelated server changes.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Modify loot with Better Loot

Better Loot is the usual choice when you want one plugin to control general container behavior and separate loot tables for different container prefabs.

Understand Better Loot’s two locations

  • oxide/config/BetterLoot.json contains global settings. This is where you should look for plugin-wide behavior such as multipliers, exclusions or other options exposed by your release.
  • oxide/data/BetterLoot/LootTables.json contains per-container loot data in current documentation. An older forum post used the singular name LootTable.json; do not create a second file based on that post. Check which file your installed plugin actually creates, with the plural name treated as the current default.

Paths are relative to the server installation. On Carbon, do not assume that the Oxide paths are identical; verify the plugin’s Carbon instructions and the directories it creates.

Step-by-step Better Loot workflow

  1. Stop the server or unload Better Loot using the framework’s documented method.
  2. Back up the complete oxide/config/BetterLoot.json file and the oxide/data/BetterLoot/ directory.
  3. Open the global configuration and identify the option you need. Do not paste an example from a different release without matching its property names to your file.
  4. Open LootTables.json and locate the container or prefab entry you intend to change. Preserve the existing nesting and data types.
  5. Add, remove or adjust only the item records needed for the test. Keep item short names exactly as expected by the plugin; an invalid short name may be skipped or logged as an error.
  6. Save both files and validate each as JSON. Validation confirms syntax, not that the plugin understands every field.
  7. Reload Better Loot with oxide.reload BetterLoot on Oxide/uMod, or use the equivalent Carbon reload command documented for your server.
  8. Read the console for parse errors, unknown properties and missing dependencies. If the plugin rewrites the file, compare the result with your backup before making another edit.
  9. Test a newly generated container in a controlled area and confirm that the result matches the table you changed. Existing containers may have been generated under earlier data, so use the plugin’s documented regeneration behavior rather than assuming every container changes immediately.

Upgrading to Better Loot V4

Do not copy an older Better Loot table directly into version 4. The uMod documentation states that V4 is incompatible with old loot-table files and points to a converter at looty.cc/converter. Preserve the pre-upgrade files, convert a copy, inspect the generated JSON, and test it before replacing the live data. If the converter or the release notes do not cover your version, ask the plugin author or follow the release-specific migration instructions instead of guessing field mappings.

Modify loot with MagicLoot

MagicLoot separates its general configuration from stack-size data, so editing one file for the other purpose will not produce the expected result.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Rank #3
BladeHawks RGB Gaming Mouse Pad Extra Large Extended 31.5x12 Inch-Black
  • 【Large size】:Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
  • 【LED backlight mouse pad】:Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
  • 【Anti-slip rubber base】:Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
  • 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
  • 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
  • oxide/config/MagicLoot.json contains container multipliers, blacklists and per-container rules.
  • oxide/data/MagicLoot.json contains stack-size data.

Change multipliers, exclusions or container rules

  1. Back up both MagicLoot files, even if you intend to change only one.
  2. Stop or unload MagicLoot before a manual edit when practical.
  3. Open oxide/config/MagicLoot.json and find the relevant multiplier, blacklist or container-specific section supplied by your release.
  4. Change one value, retaining its original type. A numeric multiplier should remain numeric; do not quote it unless the plugin’s schema shows a string.
  5. Validate the JSON and reload MagicLoot with oxide.reload MagicLoot on Oxide/uMod.
  6. Check the console and test a newly generated container.

Change stack sizes

  1. Open oxide/data/MagicLoot.json, not the configuration file.
  2. Locate the item entry and edit its stack-size value using the format already present in your file.
  3. Check whether the item is also affected by a container multiplier or another plugin. A valid stack-size edit can still appear ineffective if another rule caps or replaces it.
  4. Validate, reload and test. Keep a copy of the original data so you can restore only the affected item if the result is too generous.

MagicLoot’s documentation does not establish a universal set of property names or numeric limits. Treat the file generated by your installed release as the schema and avoid importing fields from a different version.

Edit loot with Loot Table & Stacksize GUI

The Loot Table & Stacksize GUI plugin is useful when you want to edit through the game rather than hand-edit JSON. It has framework-specific prerequisites.

Carbon prerequisite

On Carbon, enable Harmony references first with:

c.harmonyreference 1

Run the command with the permission level required by your server, then install or reload the GUI plugin as its documentation directs. If the GUI does not open or reports missing Harmony references, check that the setting persisted and that the plugin release supports your Carbon version.

Oxide prerequisite

On Oxide, the plugin requires Image Library. Install the dependency before loading the GUI plugin, then inspect the console for a successful dependency load. A missing Image Library can make the plugin fail even when the table data itself is valid.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Safe GUI procedure

  1. Back up the relevant plugin data before opening the editor.
  2. Grant only the required administrative permission to the account that will edit loot.
  3. Open the GUI using the command documented by the installed release.
  4. Select the container or item, change its value, and use the GUI’s save or apply control rather than closing the interface abruptly.
  5. Reload the plugin if the documentation requires it, then inspect the console and test a newly generated container.
  6. If the GUI writes JSON, validate the resulting file and keep the previous backup until the change has been verified.

Because the exact command names and permission strings are release-specific and are not established here, do not substitute a command copied from an unrelated GUI version.

Rank #4
Sale
Vaydeer Wrist Rest for Keyboard and Mouse, Computer Ergonomic Wrist Support Pad, Soft Memory Foam Arm Cushion for Desk, Palm Hand Office Laptop Typing
  • 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
  • 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
  • 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
  • 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
  • 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Change loot in Raidable Bases

Raidable Bases has its own event-loot data. Editing Better Loot or MagicLoot does not replace the files Raidable Bases reads for these events.

Oxide/uMod path

On Oxide, Raidable Bases reads data under oxide/data/RaidableBases/. Default_Loot.json acts as the fallback file. Back up the directory before editing and preserve the existing structure.

Carbon path

On Carbon, the corresponding location is described as carbon/data/RaidableBases/. Confirm the actual directory created by your installed plugin rather than moving Oxide files blindly.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Generate a complete editable list

The command rb.populate all generates an editable list of every item. Use it after backing up the current data, then inspect the generated files to see which entries your release exposes. Treat the generated output as a starting point: validate it, make a small change, reload or restart as documented, and test a new Raidable Bases event.

Fallback behavior

If a specific event or profile does not have its own loot definition, the plugin can use Default_Loot.json as the fallback. Keep this file valid even when you create specialized tables, because a malformed fallback can affect events that do not use a custom profile.

Best Value
Sale
Under Desk Cable Management Tray No Drill, Metal Mesh Cable Management Under Desk with Clamp Mount, 2 Hole Cable Tray with Wire Management and Cord Organizer for Home Office Standing Desk
  • 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
  • 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
  • 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
  • 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
  • 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.

Oxide and Carbon reloads

On Oxide/uMod, the standard single-plugin reload syntax is:

oxide.reload PluginName

Replace PluginName with the plugin’s actual name, such as BetterLoot or MagicLoot. Reloading one plugin is safer than restarting every plugin because it narrows the change and makes console errors easier to identify.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Carbon provides an equivalent reload mechanism, but the exact command and path can differ by release. Use Carbon’s command reference or the plugin’s Carbon instructions. Do not run an Oxide reload command and assume it has applied to a Carbon installation.

How to design a loot change without destabilizing progression

Start with a measurable objective

Define the change before editing: for example, increase medical supplies in a particular container, remove a specific item from early-game crates, or alter stack sizes to reduce inventory management. A goal such as “make loot better” is too broad to test and encourages simultaneous edits that are difficult to reverse.

Change one dimension at a time

Separate item selection, quantity, stack size, container multipliers and blacklists into different test changes. If you alter all of them together, a surprising result cannot be attributed to one setting.

Use rarity labels cautiously

Community posts sometimes describe a scale of None = 0, Common = 1, Uncommon = 2, Rare = 3 and VeryRare = 4. That scale is not verified here as a universal Rust or plugin standard. Do not assume a rarity number has the same meaning across Better Loot, MagicLoot or another plugin; use the field definitions in your installed release.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Test the player experience, not just the file

  • Generate the container or event that uses the edited table.
  • Check that item short names resolve to the intended items.
  • Check quantity and stack behavior in inventory.
  • Confirm that blacklisted items do not reappear through a second plugin.
  • Review the server console after reload and after the test event.
  • Record the exact file, version and change so you can reproduce or undo it.

No published statistic establishes a standard drop rate for modified Rust loot. Your server’s results depend on the plugin’s algorithm, table values, container type and other active plugins, so measure your own test results rather than presenting a community rarity label as a probability.

Troubleshooting common failures

Symptom Likely cause Recovery
Plugin will not load after editing Invalid JSON, wrong data type or an unknown field Restore the backup, validate the file, then reapply one change at a time while checking the console.
Changes are ignored Edited the wrong framework path, wrong file, or an older filename Confirm Oxide versus Carbon, inspect the file the plugin actually created, and verify the installed release’s documentation.
Manual edits disappear The loaded plugin saved its in-memory data over the file Stop or unload before editing, reload only after saving, and compare the file before and after reload.
Better Loot reports table errors after an upgrade Old table format used with Better Loot V4 Restore the original, use the documented converter on a copy, and test the converted data.
GUI does not start on Carbon Harmony references are disabled or the release is incompatible Run c.harmonyreference 1, reload according to Carbon’s instructions, and verify the plugin version.
GUI fails on Oxide Image Library is missing or failed to load Install and load Image Library first, then inspect dependency errors before reloading the GUI plugin.
Raidable Bases loot remains unchanged The edit was made in Better Loot or the wrong data directory Use the Raidable Bases directory, check Default_Loot.json, and regenerate an item list with rb.populate all if needed.
Only some containers change Different prefabs or profiles use different tables Identify the exact container entry or event profile and test it separately from the global settings.

Maintenance checklist

  • Keep a dated backup before every table migration or bulk edit.
  • Record the Rust build, framework, plugin version and file path.
  • Validate JSON before every reload.
  • Reload only the edited plugin where the framework supports it.
  • Read the console for parse, dependency and unknown-field errors.
  • Test newly generated containers or events on a test server first.
  • Do not combine Oxide and Carbon installations on one server.
  • Recheck file names and field names after plugin updates, especially when moving to Better Loot V4.

The reliable pattern is simple: use the plugin that owns the loot you want to change, edit its version-matched file or supported GUI, validate the result, reload narrowly, and verify an actual newly generated container or event. That approach avoids changing a file no plugin reads and gives you a clean rollback when a table or dependency fails.

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.