From nothing to a running Rust server

Everything DropLaunch does on a real PC, in order. Steps tick off as they happen in the window: downloads, the server and Rust are simulated.

0 of 15 done

1One-click setup

A Rust server needs two things from Valve: SteamCMD and the server files. One click gets both, plus a mod framework and the start files.

Do itClick Set up a server on the welcome screen. Closed it? Fix it on the Maps page opens the same setup.
Valve's command-line Steam client, the tool every Rust server is installed with. DropLaunch downloads it and lets it update itself on its first start.

On your PCDropLaunch\SteamCMD\steamcmd.exe

Do itNothing to click: it runs by itself once the setup starts.
SteamCMD signs in anonymously and downloads Rust's dedicated server, about 6 GB. Only once: an update later gets just what changed.

On your PCDropLaunch\Server_Files\RustDedicated.exe

Do itNothing to click. On a real PC this is the long part, 5 to 30 minutes: Hide keeps it going while you look around.
The mod framework that runs plugins. The RustEdit extension is for maps that use RustEdit features, and the DropLaunch plugin lets testers send bug reports with /bug.

On your PCCopied into DropLaunch\Server_Files

Do itPick one under Mods in the setup window while the server downloads. Carbon is the default.
start_procgen_server.bat starts the server with DropLaunch's settings: ports, RCON and the map. update_server.bat runs SteamCMD to update it. Both work without DropLaunch too: double-click them.

On your PCDropLaunch\Server_Files\start_procgen_server.bat update_server.bat

Curious?See what goes in one with the start file generator.
DropLaunch runs the start file. The server opens in its own console window, and DropLaunch reads its log to show how far it is.

Do itWith Run test map server on, press Continue when the setup is done. Otherwise press play next to any map on the Maps page.

2Your first server

The server loads the game files, starts Carbon and generates the map. The first start takes a few minutes on a real PC; DropLaunch shows each stage.

Do itWatch the bar at the bottom of the Maps page until it says Ready.
Join starts Rust, or uses the one that's open, and connects you. Without DropLaunch it's F1 in Rust and client.connect 127.0.0.1:28015.

Do itClick Join in Rust once the server is ready.

3Test your own map

Maps in DropLaunch's Maps folder show in the list. Dropping a .map file on the window, or on DropLaunch.exe, starts it straight away. The running server is stopped first.

Do itPress play next to a map under Active folder. You can also drop any file ending in .map on the window.
Two .bat files for that map: one starts it normally, one in prefab test mode for unfinished maps (no cargo ship, boat paths or events). Start the map without DropLaunch, or send them to a friend.

On your PCServer_Files\start_Canyon_Rally_v18.bat start_Canyon_Rally_v18_prefab.bat

Do itRight-click a map and choose Create start files.
With the DropLaunch plugin, testers type /bug and a few words in Rust's chat. The report lands on a map of your island, where they stood. In the demo, testers join and send some on their own.

Do itClick More options and open Bug reports once one has come in.

4Run the server

The console shows the server's log and sends commands over RCON. Try status to see who's online.

Do itClick More options, type in the box under the console and press Enter.
Hand a kit to anyone on your server, like the built-in Basic Build Kit, without typing item names in the console.

Do itIn More options, open Give items, pick a kit and a player.
Stop saves the world, then closes the server's window. Restart does the same and runs the start file again.

Do itClick Stop in the server bar.
When Rust updates, DropLaunch runs SteamCMD again, like update_server.bat does, and puts Carbon or Oxide back. The pill at the top says when a new build is out.

Do itWith the server stopped, open Server files (in More options) and click Verify files. When there's a new build, Update shows next to it.

Download