Creating a secret RUST server
This guide will cover the steps for creating a secret RUST server. By the end of this guide, the server owner will have installed a uMod plugin that rejects player connections that have not been granted permission to the server and allows those players that have. server owners may wish to create a individual RUST waiter for a kind of reasons, such as :
- A private clan or team practice server
- A private access server for paid or subscribing members
- Designing special events or roleplay server
- Planning, custom map or plugin testing server
Whatever the cause, it ’ mho surely helpful to have a denounce prime set up before allowing players to connect to a server that ’ mho presently being configured. In order to begin, there are two pre-requisites :
Reading: How To Create a Private RUST Server
Steps for creating a private RUST server
dance step 1 : locate and download the whitelist plugin
navigate to the uMod page for Wulf ’ sulfur Whitelist plugin, then click on the download release. This will download the latest translation of the plugin, mechanically saving the file Whitelist.cs
to your calculator. note that this template uses a specific plugin, but other whitelist plugins will work a well, a farseeing as they are compatible with RUST .
step 2 : Install the whitelist plugin
once the whitelist plugin is downloaded, make sure to save the RUST server and stop the waiter process. For this dance step you must have access to one of the adopt :
- Direct access to the server’s files
- FTP access to the server’s files
- Control panel/File Manager access to the server’s files
then in the RUST server ’ south root directory, locate the oxide folder. Inside of the oxide folder expression for another folder labeled “ plugins ”. The folder ’ s path will look like to this :
/*server_identity*/oxide/plugins/
then copy or upload the Whitelist.cs
file into this folder .
step 3 : Configuring the whitelist plugin
This plugin makes consumption of the Oxide permissions system, meaning that whitelist permissions are performed through award or revoking access to license groups or individuals. This guide does not walk through the uMod ( Oxide ) permission system, only through what is necessary to get the Whitelist plugin working. There are two default groups with uMod ( Oxide ) :
- Admin
- Default
The plugin mechanically grants access to the admin group and denies access to the default group. These settings can be modified in the plugin ’ mho configuration file located below :
/*server_identity*/oxide/config/Whitelist.json
step 4 : Granting whitelist permissions
After the Whitelist plugin is installed, start up the RUST server. Once the waiter has finished initialize, perform a quick test of the permissions set to the admin group. Copy the line below into the server comfort and compress embark :
oxide.show group admin
The server console table will return the following :
Group ‘admin’ players: 64_bit_steam_id (Steam_User_Name) Group ‘admin’ permissions: No permissions currently granted
nowadays grant the admin group the whitelist.allow
permission. Copy the line below into the server comfort and bid embark :
oxide.grant group admin whitelist.allow
The server comfort will return the adopt :
Group ‘ admin ’ granted permission ‘ whitelist.allow ’
test that the admin group has the newly added whitelist.allow
license. Copy the argumentation below into your server comfort and press enter :
oxide.show group admin
The waiter console will return the comply :
Group ‘admin’ players: 64_bit_steam_id (Steam_User_Name) Group ‘admin’ permissions: Whitelist.allow
alternatively, to manually whitelist a musician copy the line below into your waiter console and bid insert :
oxide.grant drug user 64_bit_steam_id whitelist.allow
The waiter cabinet will return the watch :
Player ‘64_bit_steam_id (64_bit_steam_id)’ granted permission ‘whitelist.allow’
To revoke the whitelist access, copy the line below into your server console and press enter :
oxide.revoke exploiter 64_bit_steam_id whitelist.allow
The waiter console will return the comply :
Player ‘64_bit_steam_id (64_bit_steam_id)’ revoked permission ‘whitelist.allow’
step 5 : Verify proper license functionality
Below is the message that the non-whitelisted musician will receive : This is the nonpayment text provided for the rejection message and can be changed in the plugin ’ s terminology configuration file, located below :
/*server_identity*/oxide/lang/en/Whitelist.json
Below is what the server side sees when a non-whitelisted musician attempts to join : The following step is to verify that whitelisting works by granting whitelist license to a player. Copy the line below into your server console and crusade embark :
oxide.grant drug user 64_bit_steam_id whitelist.allow
The server console will return the keep up :
Player ‘64_bit_steam_id (64_bit_steam_id)’ granted permission ‘whitelist.allow’
adjacent, have the player attack to connect now that they are granted the whitelist permission :
compendious
now that the whitelist plugin has been successfully installed and configured on the RUST waiter, players and oxide groups can now be whitelisted as desired. This plugin is frequently used in bicycle-built-for-two with 3rd party subscription services that grant and revoke permissions for subscribing players .