Advanced ▶ Video guide Updated September 25, 2026

Terminal and Full Box

Open a real Linux shell inside your SLASHPLAY server, install tools with apt, edit the boot script, and learn what persists, what resets and what it costs.

0:00 / 1:29
Read the transcript

This audio was created with Boson AI's Higgs Audio: boson.ai/higgs-audio

Every SLASHPLAY server runs in its own Linux container, and you can get a shell inside it from the browser. Combined with Full Box mode, which is on for every server, that container behaves much like your own small Linux machine: you can install packages, download files and change how the game starts. This page is for people comfortable with a command line.

Before you start

  • The server must be live. Otherwise the tab says The server must be running to open a shell.
  • You need the Control servers permission. See Roles and permissions.

Open a shell

  1. Open the server page, then Advanced → Terminal.
  2. Nothing connects until you ask. Click Connect.
  3. When the status line says ● Live shell, you’re inside your server’s container. Type commands as in any Linux terminal.
  4. Click Disconnect when you’re done.
The Terminal tab before connecting: a dimmed panel that says nothing connects until you say so, and a Connect button
Nothing connects until you click Connect.
A live shell in a CS2 server: the status line says Live shell and the terminal shows the start of .slashplay/boot.sh
A live shell inside the server's container.

The shell closes when you leave the Terminal tab (the page asks you to confirm first) or reload the page. No sessions linger in the background. If the session ends, click Reconnect to start a new one. If you resize your browser window, reconnect for the terminal to fit the new size.

What persists and what doesn’t

The container itself is thrown away every time the server stops, and a fresh one is built on the next start. What comes back depends on where a change was made:

WhereWhat happens at the next stop
Your server’s saved files (the world, configs, owned folders)Saved with the server and restored on start.
SlashPlay’s shared game files (the locked files in the file manager)Reset to the standard copy. Take ownership of a folder in the file manager to keep changes to it.
Everything outside the game folder (installed packages, tools, /etc edits, your home folder)Saved by Full Box and restored on start, billed as storage.

The terminal’s own reminder, Changes outside your saved paths reset at the next stop, is about the game folder. See File manager for which game files are saved.

Full Box mode

Full Box is shown under Advanced → Launch & Boot and is on for every server. It means:

  • Install anything. apt, wget and git work, with web access on ports 80 and 443, so you can download tools, plugins and files straight onto the server.
  • Your system changes are kept. Everything you change outside the game folder is saved with the server and counted toward your storage like saves. The panel shows how much is currently stored.
  • You control how the game starts. The start script is a file you can edit: .slashplay/boot.sh.
The Full Box mode panel on the Launch & Boot tab with the Reset system changes and Reset boot script buttons
Full Box mode on the Launch & Boot tab, with its two reset buttons.

The boot script

.slashplay/boot.sh is the script that starts your game. SlashPlay generates a default one from the game’s standard start command, including your launch args. You can edit it to run something before the game starts, or to change how the game is started. Changes apply the next time you click Restart server.

If you break it, restore the default: click Reset boot script on the Launch & Boot tab (the server must be running) and confirm. Your edits to the script are lost; nothing else is touched. Then click Restart server.

Reset system changes

If your installed packages or system edits cause trouble, throw them all away:

  1. Stop the server.
  2. Click Reset system changes on the Launch & Boot tab and confirm.

This deletes everything installed or changed outside the game folder. Game files and saves are not touched. The next start boots a clean system. The button is disabled when there are no saved system changes yet.

If the last system save failed, the panel says Last system save failed: with the reason.

Storage

Anything you install counts as stored data at 1 token per GB per month, from the team’s balance, for as long as the server exists. A few small tools cost almost nothing; a large toolchain or downloaded dataset can add up. Clean up what you don’t need, or use Reset system changes. See Storage costs.

Troubleshooting

Connect does nothing, or the session ends right away. Check the server is still live, then click Reconnect.

The game won’t start after I edited boot.sh. Click Reset boot script (while the server is running) and Restart server. If the server is stuck crashing, check the crash box’s last output.

Something I installed is gone after a restart. If it was inside SlashPlay’s shared game files, it was reset. Take ownership of that folder in the file manager, or install it outside the game folder.

My storage cost went up. System changes are saved and billed. Remove what you don’t need, or reset system changes.