Setting Up Dangerous Treasures Events on Your Rust Server

What This Plugin Does

Rust is already a punishing game on a quiet day, and a busy dedicated server only sharpens the edges. Still, when the player count dips, the world can feel a little too peaceful for a survival shooter. Dangerous Treasures fills that gap. It is a uMod plugin that spawns a guarded loot event somewhere on the map, surrounded by hostile NPCs and a sizeable chest full of gear worth fighting over. You can fire it manually or on a timer, turning a slow evening into a scramble where players race each other (and the AI) for the spoils.

The whole setup lives inside your server panel and only takes a few minutes. If plugins are new territory for you, this walkthrough covers every step, from downloading the file to tweaking the configuration.

Grabbing the Plugin File

Start on the Dangerous Treasures page on the uMod website and hit the Download button on the right side of the listing.

Save the file somewhere you will remember. You only need it for a minute.

Uploading to the Server

The plugin lives inside the Oxide folder of your Rust server, so an FTP upload is the cleanest way in. Open the FTP file manager from your control panel, near the top of the dashboard.

Enter your FTP password and click Login.

Navigate into the oxide directory, then into its plugins subfolder.

Click Upload at the top of the page and drop the file into the upload area, or browse to it manually.

Once the upload reaches 100%, head back to the main panel and restart the server. Hop in once the boot finishes to confirm the plugin loaded without errors.

First Impressions Inside the Game

You will not see any obvious changes after restarting. Dangerous Treasures only kicks in once an event is triggered, either by an admin command or on a schedule you define. When an event fires, missiles rain down on a chosen spot on the map and NPCs patrol the area. These enemies hit hard, so anyone who shows up unprepared will probably respawn quickly. The event ends as soon as a player clears the guards and cracks open the chest.

Every aspect of the activity can be customized, including the items inside the chest. The sections below cover the essentials so you can get started fast.

Triggering an Event

The in-game command to launch an event is `/dtevent`. To run it from chat, your account needs the `dangeroustreasures.use` permission. If you would rather skip permissions for now, type `dtevent` directly into the server console and it will fire just the same.

Two chat messages appear globally when the event starts: one with the location and one with the countdown until the chest fully activates.

The delay before activation is configurable, which gives players time to gear up and travel. If anyone struggles to find the spot, the `/dtd` command shows their distance to the next event and can also preview future ones if scheduled.

What Drops From the Chest

The loot pool is broad: pistols, rifles, shotguns, armor, tools, ammunition and assorted materials. Each entry can be added, removed or reweighted from the configuration file. The full default list lives inside that config, which the next section covers.

Useful Commands

There are several commands available beyond the two already mentioned, but most require either admin rights on the server or the matching permission node assigned to your player account. The uMod listing for Dangerous Treasures keeps the canonical reference, so check it for the complete command list if you start hitting limitations.

Editing the Configuration

The configuration file is where you change loot, NPC difficulty, event timing and almost everything else. Values are either numbers or true/false toggles, which keeps editing painless even if you have never touched a plugin config before.

To open it, head back into the FTP file manager from the panel and log in with your password. Walk through to `.../oxide/config`.

Find `DangerousTreasures.json` and click Edit on the far right.

Make your changes and hit Save at the top of the editor.

Back on the main panel, restart the server so the new values load.

Troubleshooting

If the plugin fails to load, the usual suspect is the upload path. Confirm the file sits inside `.../oxide/plugins` on the correct server profile, since each profile keeps its own directory tree. After fixing the path, restart the server and watch the console for load messages.

Permissions are the other common snag. Being an admin grants access to most commands, but it is still worth assigning the plugin's permission nodes to your own account so nothing is gated unexpectedly. If a command is rejected even after that, double-check the syntax against the uMod page.

Related Reading

• Dangerous Treasures on uMod
• Becoming a Rust Server Administrator
• Oxide Permissions Guide
• How to Access Rust Servers via FTP