keepcalculator

06 Numbers and Powers

Rust Console Commands: Players & Admins

Card No. 06·40257 · Updated · Standard formula, shown below

Rust console commands let players and server admins control game settings, manage servers, and troubleshoot issues directly from the in-game console or server terminal. This article lists the most useful commands for both groups, explains how they work, and covers common pitfalls.

Opening the Console

Before using any command, you need to know how to open the console. On PC, press F1 (default) while in-game. On console versions (PlayStation and Xbox), the console is not available in the same way—most admin commands are done through the server’s RCON or a third-party tool. On PC, the console accepts both client-side and server-side commands depending on the context.

Essential Commands for Players

These commands affect your local client and often improve performance or change how the game looks or feels.

  • fps.limit <number> – Caps your frame rate. For example, fps.limit 60 limits to 60 FPS, which can reduce heat and power draw.
  • graphics.quality <0-100> – Sets overall graphics quality. graphics.quality 0 is the lowest, 100 is the highest.
  • render.vsync <true/false> – Toggles vertical sync to prevent screen tearing.
  • input.mouse_sensitivity <number> – Adjusts mouse sensitivity. Lower values are slower.
  • player.thirdperson <true/false> – Switches between first-person and third-person view (on servers that allow it).
  • combatlog – Prints a log of recent combat actions to the console, useful for reporting bugs or cheating.
  • client.connect <server_ip:port> – Connects directly to a server by IP.
  • quit – Closes the game immediately.

Most client commands are saved in your cfg/client.cfg file and can be edited manually for persistent changes.

Essential Commands for Server Admins

Admins use the console (or RCON) to manage the server, players, and world. These commands are typically entered in the server console or via the in-game console if you have admin privileges.

  • server.writecfg – Saves current server settings to server.cfg. Always run this after changing settings.
  • server.save – Forces a world save immediately.
  • server.quit – Stops the server gracefully.
  • ban <steamID> <reason> – Bans a player by Steam ID. For example: ban 76561198000000000 Cheating.
  • kick <steamID> <reason> – Kicks a player without a ban.
  • unban <steamID> – Removes a ban.
  • find <partial_name> – Searches for a player by partial name and returns their Steam ID and ping.
  • give <steamID> <item> <amount> – Gives an item to a player. Example: give 76561198000000000 wood 500.
  • teleport <steamID> <x> <y> <z> – Teleports a player to coordinates.
  • status – Shows connected players, their Steam IDs, and ping.
  • cair <true/false> – Toggles the in-game admin panel (requires admin flag).

Admin Flags and Permissions

To use admin commands, your Steam ID must be in the server’s admin.cfg file or you must have the appropriate permission flags. The ownerid command adds a player as owner with full access:

ownerid <steamID> "reason"

Other flags include moderatorid for limited moderation. Permissions are checked against the users.cfg file. If a command doesn’t work, check that your Steam ID is correctly listed and that you have the required flag.

Common Mistakes and Troubleshooting

One frequent mistake is using client commands on the server console or vice versa. For example, fps.limit is client-only and will error on the server. Another issue is forgetting to run server.writecfg after changes—settings revert on restart. Also, admin commands often require the full Steam ID (17 digits), not the display name. If a command seems to do nothing, check the console output for errors; it usually tells you if you lack permission or mistyped.

Server Configuration File

Most server settings are defined in server.cfg in the server’s root folder. You can edit this file with a text editor, but changes require a restart or server.writecfg to apply. Common settings include:

  • server.hostname "My Server" – Sets the server name.
  • server.maxplayers 100 – Limits player count.
  • server.identity "my_server" – Sets the save folder name.
  • server.seed 12345 – Sets the world generation seed.
  • server.worldsize 4000 – Sets map size in meters.
  • server.tickrate 30 – Sets simulation tick rate (default 30).

Always back up server.cfg before making changes.

Frequently Asked Questions

How do I bind a command to a key?

Use the bind command in the console. For example, bind p "fps.limit 60" sets the P key to cap FPS at 60. Bindings are saved in cfg/binds.cfg.

Why does my admin command say “unknown command”?

This usually means you’re typing it in the wrong console (client vs server) or you misspelled it. Check the exact syntax and ensure you’re using the correct console for that command.

Can I use console commands on a server I don’t own?

Client commands that affect your local game (like graphics) work on any server. Server commands (kick, ban, give) require admin permission, which only server owners can grant.

How do I find a player’s Steam ID?

Use the status command in the server console. It lists connected players with their Steam IDs. Alternatively, you can use third-party Steam ID lookup tools from a player’s profile URL.

Is there a way to undo a ban?

Yes, use unban <steamID> in the server console. The player will be able to join again immediately.

Do console commands work on the console versions of Rust?

No, the PlayStation and Xbox versions do not expose a console. Server administration on those platforms is done through the server’s RCON or third-party management tools.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →