server.tags (Rust server ConVar)
Valid server.tags values for the Rust server browser, the one-per-group rule, the four-tag display limit, the tag server.pve adds, and the cfg line.
Last updated Verified on Rust build 25582902, 2026-09-28
- Kind
- Variable
- Value on build 25582902
""- Server help text
- Comma-separated server browser tag values (see wiki)
- Applies
- Immediately (runtime)
- Persists in
- server.cfg
- Vanilla Rust
- Yes, native
- Example
server.tags "weekly,vanilla,EU"
Gotchas
- Comma separated. Tags in the same group (monthly, biweekly, weekly; vanilla, hardcore, softcore) are mutually exclusive.
- The server browser shows up to four tags.
- Order does not matter, so compare values as sets, not strings.
- server.pve adds the PvE tag by itself.
- server.writecfg saves it to serverauto.cfg, but server.cfg is read after that file and wins.
server.tags sets the tags the Rust server browser shows for your server and lets players filter on. The server's help text: "Comma-separated server browser tag values (see wiki)". The value is one string, tags separated by commas.
Valid tags
These are the values in Facepunch's server browser tag reference. Only three groups exist:
| Group | Tags |
|---|---|
| Wipe schedule | monthly, biweekly, weekly |
| Difficulty | vanilla, hardcore, softcore |
| Region | NA, SA, EU, WA, EA, OC, AF |
| No group | pve, roleplay, creative, minigame, training, battlefield, broyale, builds, tut, premium |
Tags in the same group are mutually exclusive, so pick at most one per group: a server cannot wipe weekly and monthly. Facepunch warns that the browser shows only one tag from a group, and that setting two breaks search, so your server can drop out of results for a tag players filter on. Facepunch also says only up to four tags are displayed at a time, so choose the four that matter most to players.
The reference also lists Modded, Oxide and Carbon, but with no value to put in server.tags.
Setting it
It changes at runtime, over RCON or in the server console:
server.tags "weekly,vanilla,EU"
In server.cfg use the same line. To remove every tag, set an empty string, server.tags "".
Order does not matter to players. It matters to scripts: weekly,EU and EU,weekly are the same tags as different strings. If you check the running value against your config, compare the tags as sets.
Tags you do not set
server.pve adds the PvE tag by itself, according to Facepunch's tag reference, so you do not need pve in server.tags for a PvE server.
Where the value persists
server.writecfg saves server.tags to serverauto.cfg; our test server had the line there. The server's generated help text for server.readcfg says it runs serverauto.cfg first and then server.cfg, so a line in server.cfg wins. Keep the tags in server.cfg.
In Panelra
Browser tags are under Settings and apply instantly over RCON. Panelra always writes a server.tags line to the server.cfg it regenerates, even when it is empty, so removing the last tag clears it on the next config reload instead of leaving the old tags in place. Panelra compares the running tags with your settings as a set, so a different order is not reported as drift, and it leaves modded, Oxide and Carbon out of that comparison because they are not tags you set.
Set it in Panelra
Change server.tags from the dashboard instead of editing files over SSH.
Frequently asked questions
How many tags can a Rust server have?
Do I need to add the PvE tag myself?
Related ConVars
- server.pve(Generated) Enables PvE mode - players cannot damage other players; they can still be killed by NPCs and the environment
- server.hostname(Generated) Server name displayed in the server browser
- server.readcfg(Generated) Reads and executes serverauto.cfg then server.cfg from the server's cfg folder, applying all saved convar values
Skip the manual work: install the Panelra agent
Wipes, updates, restarts, plugins and crash alerts for your Rust servers, from one dashboard. One install command on your Linux host, no inbound ports for the agent.
Free during the open beta. Pricing will be announced before the beta ends.