Server Administration

There are a number of commands that can be executed on a running dedicated server while being in-game. With these commands you can control how the server runs.

There are commands that a available to all player, even public players - those commands are called public commands. All other commands require the player to be assigned a specific access level by a server administrator.

In order to enter a command, you have to open the console. On an English keyboard you access the console by double tapping the ` (tilde) key on your keyboard. If this does not work for you, an easy workaround is to press the AllChat key J on your keyboard and then press backspace and remove the current command "ChatToAll" - now you have the console open and ready to use. You can repeat old commands in the console by pressing the cursor Up key. With the cursor Up Down keys you can also scroll through your command history and execute it with Enter.

If you face any problems with your server, please go to Server Troubleshooting.

Admin Access Levels
The following table lists the existing access levels. Please note that all players have access to the public commands; there is no access level for public commands.

Access levels need to be assigned to individual users - see section "Adding Admins in Admins.cfg" for more details on this. Only the server administrators of the dedicated server in question can set these and they will only apply to this server.

Admin Console Commands
When it says  you're supposed to free text it.

Check AdminKick for further details.

Public Commands
When it says  you're supposed to free text it.

Spectator Camera
The spectator camera (often also called "admin camera" or "admin cam"), a semi-free movement camera, is a very useful feature for clans and tournament hosts or if you want to have full camera control when recording gameplay videos of Squad.

You need to have access level "cameraman" in order to use the camera. There is one exception: on Firing Range all players can use the camera.

While in the camera, you soldier character will be invisible. When you exit the camera if you are on a server, you'll resume from where you've entered the camera. If you exit the camera when you are in the local shooting range, you spawn your character model at the camera's current position (beware of heights - you die from high falls)

If you want to record pure gameplay footage without any HUD elements, you can use the public command "SetHudWidgetsEnabled 0" or the screen shot mode. To hide ammo symbols make sure do disable "Ingame help" in Settings > Interface.

If you want to watch from both team's sides, you will have to switch teams to see the other side.

OWI is constantly improving and adding functionality to the spectator camera, however please be aware of some known bugs and problems:
 * Very rarely when exiting the camera you get glitched. In this case you will need to suicide to respawn.
 * While seated in a vehicle do not enter the spectator camera.
 * If, after exiting the camera, your character arms do not move, you will need to suicide to respawn.
 * If you switch teams twice without leaving the camera you sometimes will completely glitch out and need to restart Squad.
 * If you use player stencils without having HUDViews turned on, the outlines will ghost.

The following table shows all available controls of the spectator camera. All controls only work if you have the spectator camera turned on.

Vehicle Spawn Commands
You can use copy & paste from the wiki straight into the console in Squad, so you don't have to type the command out manually. You can also repeat old commands by pressing the cursor Up key in the console.

If you get the message "Invalid Class! (Did you forget the '_C'?)", you have misspelled or gotten some additional characters into your command. Try again. Review your command in the console history - this might help you spot your typo.

Please note, you can ONLY spawn vehicles on unlicensed servers with the featuretest admin permissions or on a local server.

If you want to look up the command for a completely new vehicle, you have to use the Squad SDK and follow these instructions:
 * Start the Squad SDK
 * Look under the 'Content' folder (Content/Vehicles), each vehicle has its own folder. Each variant will have a Blueprint, right-click on this and select 'copy reference' (see image below).
 * This will give you a string. Example: Blueprint'/Game/Vehicles/BRDM-2/BP_BRDM-2_RUS_Desert.BP_BRDM-2_RUS_Desert'
 * Change this string into a Squad in-game console command by adding "_C" at the end. Example: AdminCreateVehicle /Game/Vehicles/BRDM-2/BP_BRDM-2_RUS_Desert.BP_BRDM-2_RUS_Desert_C
 * Test the spawn command in the Shooting Range.
 * Add the command to the tables below.



* Unreleased vehicle

Getting Crash Dumps
Crash dumps are helpful files that show more advanced system details at the time of a server crash.

Linux
1. Navigate to your squad server direcotry.

2. Navigate to the following file:

.../SquadGame/Saved/Config/LinuxServer/Engine.ini

3. Add these additional lines:

[CrashReportClient] bAgreeToCrashUpload=true

4. Create a crashes folder at:

.../SquadGame/Saved/Crashes

ALL CHANGES BELOW HERE IMPACT SYSTEM WIDE SETTINGS AND ARE ONLY REQUIRED FOR FULL COREDUMP/CRASHDUMP FILES.

5. Make sure ulimit for cores is greater than 0. Having too small of a number may result in core dumps being cut off.

Run this command in any terminal: ulimit -c unlimited

It may also be necessary to increase the per process file handle limit:

This should only be done if your crash log has error "failed: errno=24 (Too many open files)" as a log line right before the callstack at the end of the log ulimit -n 2048

or alternatively editing your limits.conf file.

Changing these limits will require the SquadGameServer is restarted.

6. On systemd based distros (ubunto/debian) the *systemd-coredump* package may also be required.

You can install this by running this command in any terminal:

apt install systemd-coredump

It is suggested to adjust systemd settings regarding core file size or you may see core dumps being cut off.

Navigate to /etc/systemd/coredump.conf and edit the following lines:

ProcessSizeMax=10G ExternalSizeMax=10G

A server restart is required for the settings changed to take effect.

Crash Minidump and logs will appear in: SquadGame/Saved/Crashes/

Each crash will create its own folder labeled: crashinfo-SquadGame.../ *

Full core dumps will be created where your system creates core dumps. For systemd-coredump systems they will be located in:

/var/lib/systemd/coredump/

It is possible to force a crashdump by using this command in any terminal:

kill -SIGSEGV $pid

Replace pid with the process id of the SquadGameServer process.