Summary This guide is designed to help you understand Oxide’s permission system. It will cover the basics of what a permission is, how to give them to your players, and how to work with Oxide’s group system. Permissions Oxide allows you to add various plugins to your server which can alter gameplay through various commands or functionalities. Many of these features have associated permissions, allowing you to control who has access to each of them. In short, permissions are simply a string or sequence of letters and digits, commonly separated into sections using periods. These sections are referred to as “permission nodes” or “nodes” for short. Our example plugin features a few different permissions, for instance enhancedbansystem.banlist. When a user has this permission, it allows them to use the command /banlist Wildcards: A wildcard acts as a “grant all” for a node, and is commonly denoted by the asterisk symbol. For example, the permission enhancedbansystem.* will grant the user all permissions from our example plugin. Groups Occasionally you may want to assign the same set of permissions to multiple people. For instance, you may want admins on your server to have access to commands such as banning and kicking. Instead of assigning each user the same permissions, Oxide features the group system. Oxide’s permission groups offer the following features: Create multiple groups with any names. Quickly add and remove permissions to a group. Add and remove users from a group. Users inherit permissions from their groups. Create group hierarchies with inheritance. Inheritance When a user is assigned a group, they are not directly given the permissions, rather they inherit the permissions from the group. When called upon, the permission system will first check if the player has the permission, if not it will check if their groups do. Similarly, you may assign groups a “parent” group. The “child” group will then inherit all permissions the parent has. Below is an example of how the player Mitch inherits permissions from the Admin group, which inherits from the Mod group. Oxide’s Permission Commands Command Description Oxide.grant user “STEAMID64” “permission” Grants a permission to an individual player. Oxide.revoke user “STEAMID64” “permission” Revokes a permission from an individual player. Group Commands Command Description Oxide.group add “group-name” “[Title]” “rank” Creates a new group with the specified group-name. The title and rank are optional, but if provided sets those two values. Oxide.group set “group-name” “[Title]” “rank” Sets the title of the group. The rank is optional, but if provided sets the rank of the group. Oxide.group remove “group-name” Deletes the group. Oxide.grant group “group-name” “permission” Grants a permission to a group. Oxide.revoke group “group-name” “permission” Revokes a permission from a group. Oxide.group parent “group-name” “parent group-name” Set a parent for a group, the group will inherit all permissions from the parent. Oxide.usergroup add “STEAMID64” “group-name” Adds a user to a group. Oxide.usergroup remove “STEAMID64” “group-name” Removes a user from a group. Information commands Command Description Oxide.show user “STEAMID64” Shows the permissions a user has Oxide.show group “group-name” Shows data for a specific group. Includes permissions, parents, title, rank, and members. Oxide.show perm “permission” Shows which users or groups have this permission. Oxide.show groups Shows a list of all groups. Oxide.show perms Show all registered permissions from all plugins and Oxide. Timed Permissions Plugin Allows you to grant permissions or groups for a specific time Command Description revokeperm “player|steamid” “permission” Revoke a timed permission from a player grantperm “player|steamid” “permission” “time” Give a player a permission for a specific time removegroup “player|steamid” “group” Remove a timed group from a player addgroup “player|steamid” “group” “time” Add a player to a group for a specific time pinfo [player|steamid] Show active timed permissions and groups of a player Usage example: /grantperm GT timedpermissions.use 30d gives GT the permission timedpermissions.use for 30 days. d = days h = hours m = minutes
How to wipe a Rust server
Summary Rust servers contain large, expansive maps that players can explore and settle on to build elaborate fortresses, shops, or communities. Rust has a general progression path, making joining an existing server daunting for new players. Fortunately, users can wipe their Rust server map and start fresh at any time. Users can also customize what data they want to delete, allowing users to keep their player data while resetting the map alone or vice versa. 1. Go to your server control panel. 2. Stop the server. 3. Go to the Files tab. 4. Locate the following directory: /home/container/server/rust . 5. Delete the .db files to reset Player Data, and delete the .map/.sav files to Reset the Map. /home/container/server/rust/player.blueprints.5.db/home/container/server/rust/player.blueprints.5.db-journal/home/container/server/rust/player.deaths.5.db/home/container/server/rust/players.deaths.5.db-journal/home/container/server/rust/players.identities.5.db 11. Start the server. NOTE: Also, if you change the game map every wipe, don’t forget to change the seed and map size, or upload a new custom map. If you don’t know how to do this: How to change the world size and seed How to upload a custom map
How to upload a custom map to a Rust server
Summary Uploading a custom map to a Rust server can give players new terrain, landmarks, and environments to explore, providing unique challenges and gameplay opportunities. Rust custom maps can range from small-scale arenas to vast open worlds. It offers new experiences for players to test their survival skills in fresh and unique ways. Upload the Rust map to Dropbox first to provide a direct download link to the server. NOTE: Also, make sure to install the RUST EDIT mod. 1. Upload the .map file to Dropbox. 2. Once uploaded, click the paperclip icon next to the map file. This will copy the download link. 3. Choose the Startup tab in the Games panel. 4. In the Custom Map URL field, paste the link from the map file. Important: At the end of the link, make sure you replace the “dl=0” with “dl=1”. 5. Restart the server.
How to setup automatic server wipes on a Rust server
Summary An automatic server wipe for Rust is a set interval at which the server will be completely reset. This creates an expectable time frame for players to play around while also keeping the world fresh, which makes an excellent returning point for players. In addition, this is a fantastic time for new players to join an existing community. Wiping a Rust server is also generally good for the game’s health, as it reduces clutter and can eliminate any problems that could arise with long-running servers. 1. Go to your server control panel. 2. Go to the Schedules tab. 3. Choose Create Schedule. 4. Enter a Name in the field. 5. Set a Start Time. This is when the first server wipe will occur. 6. Choose an Interval. This will set the time between server wipes. 7. Press Create Schedule. 8. Open the created schedule, and choose New Task. 9. Choose Delete Server Files from the Action drop-down menu. 10. Enter the following file paths in the Delete File Paths field. /home/container/server/rust/player.blueprints.5.db/home/container/server/rust/player.blueprints.5.db-journal/home/container/server/rust/player.deaths.5.db/home/container/server/rust/players.deaths.5.db-journal/home/container/server/rust/players.identities.5.db/home/container/server/rust/ 11. Choose Create Task. The server will delete world and player files at the set time interval. NOTE: Also, if you change the game map every wipe, don’t forget to change the seed and map size, or upload a new custom map. If you don’t know how to do this: How to change the world size and seed How to upload a custom map