RUST Experimental servers are relatively simple to use. They are however configured somewhat differently from most games and have a learning curve as a result. With a basic understanding of how these servers operate, you will find it much easier to make changes as needed. Take a few minutes to follow the steps outlined in this Getting Started guide closely and you will be online and running with ease.
While most games use a configuration file to define settings, often called "server.cfg" or similar, RUST Experimental servers operate exclusively from the command-line. These settings are considered the "launch parameters", meaning the full list of settings the RUST server will use once it has been started. With this in mind, your first step in setting up a new RUST Experimental server will be to create a custom command-line.
- Open the RUST Server interface from the "Game Services" section in the Game Control Panel
- Navigate to the "Commandline Manager" using the available icon
- Select the "Custom Commandlines" tab at the top of the page
- Click the "New" button under this tab to generate a brand new Commandline
With a New Command-Line created using the previous steps, we will need to begin configuring it with the desired values. Keep in mind that each setting has a check-box displayed on the left hand side, where this must be selected if you wish to have that specific value included. Not all of the available parameters are required, however we will mark the ones which are to ensure your server starts properly. Use the following list of values and descriptions to get started creating yours.
* denotes a required value
- * Description - This is the name/description of the Commandline you are creating. For servers which have more than a single Commandline, this is useful to help tell them apart.
- * server.hostname - This is the server name as it will be displayed in-game and on the server browser.
- * server.identity - The server identity is basically a profile which stores all of your server data including the world, configurations, plugins, etc. Many of the features within the Control Panel rely on the default identity of "fragnet", where we do suggest keeping that set. Changing the identity to a different name will cause the Web Console and other convenience tools to cease working.
- * server.description - This is the server description, displayed when players view more information about your server in the browser. You can create separate lines by placing the characters "\n" without quotations which will denote a new line.
- server.headerimage - This should be a 512 x 256px image file in either PNG or JPG format. This will be hosted remotely using a file sharing website (ex: http://imgur.com) and the value specified is the URL to the image.
- server.url - This is the URL to a website of your choice.
- server.level - The server map which should be loaded. If a value is not specified, this will default to "Procedural Map". The only other option available at this time is "HapisIsland".
- server.seed - This is a numeric value that is used to generate the Procedural World. The value should be between -2147483647 and 2147483647.
- server.saveinterval - The number of seconds between automatic server saves.
- rcon.password - This is the Remote Console password, used for server administration using 3rd party tools such as RustAdmin.com
- logFile - This is the file which the server events and console logs are written to. The default value is "Output.txt"
- rcon.web - When enabed, this will replace the traditional RCON protocol with a Web based Protocol instead. This is intended to be used with certain types of 3rd party Web Based RCON systems
Once you have created your Commandline with the desired values, you will be taken back to an overview of all Custom Commandlines on your server. You must click "Select" on the right side to activate this Commandline, marking it as the primary one to use. After doing so, restart the server and it will launch using all of the parameters that were defined.
RUST Experimental has two types of roles for administrating a server, the Owner and the Moderator roles. To assign yourself and/or other users to these roles, you have the option of using either the configuration file or our custom tool. We will go ahead and cover both approaches, however keep in mind that these accomplish the same task.
The "Add Admins" button, located on the RUST Server interface will allow you to quickly add new users to the desired roles. Once you have opened this tool, fill in the provided fields using the following details.
- Access - "Full Access" assigns the user to the "Owner" role. "Moderator" assigns the user to the "Moderator" role.
- Steam 64 ID - This is the unique 64 bit identifier that is assigned to each player by Steam. You can determine your Steam 64 ID using a website such as https://steamid.io
- Player's Name - This is the player's in-game username
While the above steps will add new users directly to the list of Admins configuration file, you may sometimes need to directly access this file to modify or remove existing users. You can access this from the RUST Server interface under the "Configuration Files" icon. Locate the file "server\fragnet\cfg\users.cfg" and select the "Text Editor" button on the right side. Please note, if you have previously specified a different server.identity in your command-line, you will need to use the File Manager or an FTP client to locate the "users.cfg" in your identity folder instead.
Each line within the "users.cfg" file represents a different user, where the data is separated into 4 columns. The first will be either "ownerid" or "moderatorid", representing the role which they have been assigned. The second column will be the Steam 64 ID which is their unique 64 bit identifier. The last two columns are the player's in-game username and a unused value which you can use as a memo. Users added via the "Add Admins" tool will simply have this set as "Admin", although it can be used to store a real name, notes, etc.
The Steam Update button, located within the RUST Server interface, is used to automatically download and install the latest server files directly from Steam. When a new update for the game is released, the server must be updated to ensure that clients are able to connect. While this can be scheduled to take place at certain times, most sever owners will choose to do so manually, ensuring that they are able to properly notify their players before hand.
Was this answer helpful?
To install Oxide on your server, first login to your game panel, and then select your game...
Adding admins to your RUST server is quite simple. Go to http://steamid.co/ and search for your...
In case you want to use the RCon feature on your RUST server, you will have to create a new...
Login to the game panel and navigate to your game server. After that, you should see 3 tabs...
The commands below can be used with the "Web Console" Server Settings/Controls...