How toRageCOOP

RageCOOP Admin Commands and Whitelist (Management Resource)

RageCOOP has no built in admin or password. Install the Management resource to kick, ban, register users, set roles and lock the server to a whitelist.

Updated Oct 7, 2026 · 5 min read

On this page

A plain RageCOOP server has no admin commands and no password option: anything typed in the server console is just chat. Kicking, banning, registered accounts and a whitelist all come from the official Management resource. Drop RageCoop.Resources.Management.respkg into the server's Resources/Packages folder, restart, and you get /kick, /ban, /unban, /register, /unregister and /setrole, plus an AllowGuest switch that turns the server into members only. First job after installing it: remove the default admin account, which ships with a public password.

A Grand Theft Auto V street at night

Step 1: Install the Management resource

  1. Download RageCoop.Resources.Management.respkg from the releases of the official GTAV-RESOURCES repository.
  2. Stop the server.
  3. Put the file in Resources/Packages/ next to the server program. The server creates the Resources folder on first start, so create it by hand if the server has never run.
  4. Start the server. The console logs that it loaded the management database. If it reports that the resource failed to load instead, the package does not suit your server build, so try the other RageCOOP build (release or nightly) or rebuild the resource from its source.

On a GamezServers server, upload the .respkg through the file manager or SFTP into the same Resources/Packages folder and restart from the panel.

On first start the resource creates its data folder at Resources/Server/data/RageCoop.Resources.Management/, containing Config.json and the user database ManagementStore.db.

Step 2: Remove the default admin right away

When the database is empty, the resource creates one admin account:

  • Name: Sausage
  • Password: ilovesausage

This is in the public README, so anyone can log in as admin on a fresh install. Register your own account first, make it admin, then delete the default one. The server console runs commands with full permissions, so do it there:

/register yourname a-long-password
/setrole yourname Admin
/unregister Sausage

Commands start with / both in the console and in game chat. Without the slash, the line goes out to players as a chat message from "Server".

Commands

Command Permission needed What it does
/kick [username] [reason] Kick Kicks a player
/ban [username or address] [reason] Ban Permanent ban by name or IP
/unban [username or address] Ban Removes a ban
/register [username] [password] Register Creates an account with the default role
/unregister [username] All (or none, to remove yourself) Deletes an account. They are not kicked until they reconnect
/setrole [username] [role] All Moves a user into a role from Config.json

Banned players see You're banned: followed by your reason when they try to connect.

Step 3: Turn on the whitelist

RageCOOP has no server password. The Management resource's whitelist is the replacement. Open Config.json:

{
  "AllowGuest": true,
  "DefaultRole": "User",
  "Roles": {
    "Admin": {
      "CommandFilteringMode": 1,
      "Permissions": "All",
      "WhiteListedCommands": [],
      "BlackListedCommands": []
    },
    "User": {
      "CommandFilteringMode": 1,
      "Permissions": "Register",
      "WhiteListedCommands": [],
      "BlackListedCommands": []
    },
    "Guest": {
      "CommandFilteringMode": 0,
      "Permissions": "Register",
      "WhiteListedCommands": ["register"],
      "BlackListedCommands": []
    }
  }
}

Set "AllowGuest": false and restart. Now only names in the database can join, and everyone else gets You're not authorized. Register each friend from the console:

/register alex hunter2-but-longer
/register sam another-password

Each friend then opens the RageCOOP menu in game with F9, sets Username to the registered name and Password to their password, and connects. A registered name with the wrong password gets Authentication failed!. Names are matched without regard to case.

A side effect worth knowing: once a name is registered, nobody else can use it on your server, even with guests allowed. That stops impersonation in public servers too.

Step 4: Shape the roles

Roles decide who can run which commands. Three ship by default:

  • Admin: All permissions.
  • User: registered players, can run non-managerial commands not on their blacklist.
  • Guest: unregistered players (only when AllowGuest is true), can only run register by default. Do not delete this role.

Permissions takes a comma separated list from None, Mute, Kick, Ban, Register and All. To make trusted friends moderators, add a role:

"Mod": {
  "CommandFilteringMode": 1,
  "Permissions": "Kick,Ban,Register",
  "WhiteListedCommands": [],
  "BlackListedCommands": []
}

and run /setrole sam Mod.

CommandFilteringMode controls other commands, such as those added by game mode resources: 0 allows only the commands in WhiteListedCommands, 1 allows everything except BlackListedCommands.

Careful with self registration. The User and Guest roles have the Register permission by default, which lets them run /register in chat. If you run a whitelist, remove Register from those roles (set them to None) so only admins can create accounts.

Other resources from the same project

The GTAV-RESOURCES releases also offer Race, Zombies, GangWars, HandlingEnforcer and Discord packages, installed the same way into Resources/Packages. They were built over 2022 to 2024, so test each against the RageCOOP build you run before announcing it to players. Mixing in a resource built for a much older server version is a common cause of errors at startup, and the console shows which resource failed to load.

A Grand Theft Auto V scene

Running a members only server

A whitelist only helps if the server is reachable for the people on it. A GamezServers RageCOOP server gives you a fixed address with nothing to forward, a file manager for Config.json and Settings.xml, SFTP for .respkg uploads, and a live console where you run /register, /setrole and /ban as the server. One click backups keep ManagementStore.db safe, and the group can split the bill. To get the server itself running first, see how to host a RageCOOP server, and if a registered friend still cannot get in, RageCOOP can't connect fix.

FAQ

Can I set a password on a RageCOOP server?

Not directly. Install the Management resource, register your players, and set AllowGuest to false so only registered names with the right password can join.

How do I make myself admin in RageCOOP?

Run /register yourname password and then /setrole yourname Admin in the server console, then set the same name and password in the F9 menu.

What are the default admin login details?

Sausage with password ilovesausage. Delete that account with /unregister Sausage as soon as the resource is installed.

Where is the ban list stored?

In ManagementStore.db in Resources/Server/data/RageCoop.Resources.Management/. You can also edit it with LiteDB Studio.

Does RageCOOP have commands without any resources?

No. Without a resource that registers commands, console input is sent as chat.

Skip the setup. Your own RageCOOP server.

$1.49USD first month

Then $2.99/mo. Just trying it? $0.75 for 3 days

Keep reading