Space Station 14 Documentation

The project uses different licenses for code and assets:

• Code: Licensed under the MIT license.
• Assets: Most assets are licensed under CC-BY-SA 3.0. Individual asset licenses and copyright information are specified in their respective metadata files (e.g., meta.json within an .rsi folder).

Warning: Some assets may be licensed under non-commercial licenses (like CC-BY-NC-SA 3.0). These must be removed if you intend to use the project commercially.

To build Space Station 14, you must first clone the repository, initialize submodules and the engine using the provided Python script, and then compile the solution using the .NET CLI.

Note: This repository contains both the RobustToolbox engine and the content pack used for development.

The default severity for role bans is determined by the configuration variable RoleBanDefaultSeverity. If this value cannot be parsed, the system defaults to NoteSeverity.Medium and logs a warning to the admin.role_ban sawmill.

Available severity levels for the command include:

• none
• minor
• medium
• high

The config.preset_debug CVar controls whether preset debug CVars are loaded. This is a SERVERONLY variable.

Note: These presets are only loaded if the game is compiled with the DEBUG flag set.

The config.preset_development CVar controls whether preset development CVars are loaded. When enabled, certain features like lobbies may be disabled to facilitate development.

Note: These presets are only loaded if the game is compiled with the DEVELOPMENT flag set. This is a SERVERONLY variable.

Use the config.presets CVar to specify one or more configuration presets to load during server startup.

• Format: A comma-separated list of preset names.
• Requirements: Presets must be located in the ConfigPresets/ resource directory and must have a .toml extension.
• Usage: Provide only the file name without the extension.
• Scope: This is a SERVERONLY variable.

When using setbatterypercent, you may encounter the following errors:

• No battery found with id {$id}.: The provided entity UID does not correspond to a battery.
• {$arg} is not a valid float (percentage).: The percentage argument provided is not a valid floating-point number.

If the adduplink command fails, check for the following error conditions:

• Selected player doesn't control any entity: The specified player is not currently controlling any entity that can receive the uplink.
• Failed to add uplink to the player: An error occurred while attempting to attach the uplink to the player.

If the addaction command fails, check for the following error conditions:

• Invalid arguments: Ensure you have provided exactly two arguments.
• Invalid entity UID: The first argument must be a valid numeric entity UID.
• Missing ActionsComponent: The target entity must already possess an ActionsComponent to receive new actions.
• Action prototype not found: The second argument must correspond to an existing EntityPrototype ID that includes an ActionComponent.
• Adding failed: The system was unable to successfully attach the action to the entity.

If the ghost command fails, check the following error messages to identify the cause:

• You have no session, you can't ghost.: You are not currently in an active session.
• You cannot ghost right now.: The action is currently denied by the server or game state.
• You can't ghost right now. You are not in the game!: You are attempting to ghost while not actively participating in a game instance.

When using the tippy command, you may encounter the following errors:

• User not found.: The specified user could not be located.
• Prototype not found: {$proto}: The specified entity prototype could not be located.