RUST Basemission Command

RUST Basemission Command and Variable

The RUST Basemission Command and Variable

The RUST basemission command and variable is used to enable and disable missions for players on a RUST server.

This is a server-wide setting, used by admins, that applies to all RUST missions and the NPCs that provide them across the map. Unfortunately, this command does not provide any granularity to server admins for specifying which missions will be enabled or disabled.

When the RUST mission system is disabled, it does not remove the in-game UI relating to the mission system. It also does not remove the NPCs from the game world, however, the mission NPCs will refuse to grant any new missions or accept turn-ins for existing missions.

A few practical reasons for using the RUST basemission command and variable

  • Disabling and enabling the mission system on a server
  • Adding or removing the ability for players to request new missions
  • Adding or removing the ability for players to complete active missions
  • Use this setting to slow down the game progression for players

Who can use the RUST basemission command and variable

The RUST basemission command and variable can be used on vanilla RUST servers by RUST admins and moderators only. This command is not available to the general player base.

How to use the RUST basemission.missionsenabled command and variable

  • Use this command and variable to either enable or disable the RUST Missions System on a server.
  • This variable defaults to true on vanilla-based servers and accepts a true or false value as a parameter.
  • After issuing this command, it will immediately change the game world’s setting, without the server needing to restart, but does require being saved in the server.cfg or a batch startup file to persist.
  • There are some concerns for admins to consider when deciding to toggle the state of this variable
    • If this variable is disabled while players have active missions on the server, it will put them in a bugged state where they will potentially not be able to remove the active quest from their UI, whether they use the Abandon Mission button or the player.abandonmission command.
    • It’s best to not use this command after players have active missions, as there are buggy states that the game can enter where player missions will fail to be removed from the UI.
  • Note that this RUST admin command works from both the in-game console and 3rd party RCON platforms.

Getting the current basemission.missionsenabled value:

basemission.missionsenabled

On success the console will display:

basemission.missionsenabled: "True" or "False"

Enable the RUST mission system using:

basemission.missionsenabled true

On success the console will display:

basemission.missionsenabled: "True"

Disable the RUST mission system using:

basemission.missionsenabled False

On success the console will display:

basemission.missionsenabled: "False"

About dg

Dg is the founder and co-owner of Corrosion Hour, a niche gaming community established in 2016 focusing on the survival game RUST. He is an active and contributing member of numerous other RUST communities. As a community leader and server owner for over 15 years, he spends much of his time researching and writing guides about survival games, covering topics such as server administration, game mechanics, and community growth.

View all posts by dg →