Oxide (uMod) manages plugin rights through groups and users. This tool produces the series of commands to run in the server console or over RCON; it never contacts a server.
How to use the tool
Pick the prefix: “oxide.” or its short alias “o.”.
Create your groups (name, title, rank, parent group) then attach players by SteamID64.
Add the permission rows (grant or revoke) for a group or a user.
Copy the output into the server console (or over RCON). Permission names are listed by oxide.show perms.
Command syntax and points to verify
Syntax used: oxide.group add <group> [title] [rank], oxide.group parent <group> <parent>, oxide.usergroup add <player> <group>, oxide.grant <user|group> <name> <permission> and oxide.revoke in the same form. The uMod documentation covers grant/revoke; the usergroup syntax comes from community guides (SteamID64 or player name depending on the source): test on a staging server. Permissions only exist once the plugin that declares them is loaded.
Frequently asked questions
- What is the difference between “oxide.” and “o.”?
- None: “o.” is a short alias of the same commands (e.g. o.grant).
- Does it work with Carbon?
- Carbon has its own permission system; compatibility of oxide.* commands is not documented here. Check the Carbon documentation before using them.
- Where are permissions stored?
- In the server's oxide/data folder (oxide.users.data and oxide.groups.data files). Back them up before any manual change.
