Space Engineers (Torch) Guide
OS Name/Version: Windows Sever 2022
Product Name/Version: AMP Release “Proteus” v2.8.0.4, built 24/07/2026
I ran into some difficulty taking My stand alone torch install and bringing it into amp. and the guides were a bit thin so I did some digging and breaking till I figured out what worked for Me. and if anyone else needs it.. hope this helps
Setting Up a Customized Torch Space Engineers Server on AMP
1. Create the instance
- Select Application: Space Engineers (Torch)
- Give it a Friendly Name
- After Creation: Update Once
- Click Create Instance, and let the initial download/deploy finish before touching anything else.
2. Note AMP’s assigned network values
From the instance’s settings, record: Binding IP, Application Port 1 (SteamPort), Application Port 2 (ServerPort), Remote Admin Port. You’ll need these in step 5.
3. Copy the world save
Bring your world folder from your standalone server’s Saves folder into:
\AMPDatastore\Instances\<INSTANCENAME>\space-engineers\298740\servers\Saves
4. Add your plugin GUIDs to AMP’s Plugins List field
In the AMP Settings GUI, under the Torch category, find the Plugins List field and enter your plugin GUIDs, space-separated, on one line. Example — Essentials’ GUID is cbfdd6ab-4cda-4544-a201-f73efa3d46c0. Torch downloads each one automatically on next start.
5. Prep and copy your SpaceEngineers-Dedicated.cfg
Copy it to a temp location for editing. Confirm/fix these fields to match what you recorded in step 2:
IP,SteamPort,ServerPort,RemoteApiPortLoadWorld— must point to:
\AMPDatastore\Instances\<INSTANCENAME>\space-engineers\298740\servers\Saves\<WORLD FOLDER>
<Administrators>— confirm your SteamID64 (and any other admins’) is present:
xml
<Administrators>
<unsignedLong>XXXXXXXXXXXXXXXX</unsignedLong>
</Administrators>
Then copy the rest of your Torch data over:
Torchfolder\Plugins → \AMPDatastore\Instances\<INSTANCENAME>\space-engineers\298740\Plugins
Torchfolder\Instance\*.cfg → \AMPDatastore\Instances\<INSTANCENAME>\space-engineers\298740\servers\*.cfg
(The second copy brings your plugin .cfg files along. Files like players.json, ranks.json, and Essentials.KnownSteamIds.txt, essentials.cfg are connection-history/tracking data the plugin builds on its own — no need to carry those over or edit them.)
6. Import the dedicated config into AMP
In the instance’s File Manager (its own top-level sidebar item — separate from Configuration), navigate into the servers folder, right-click SpaceEngineers-Dedicated.cfg, and select Import Configuration at the bottom of the menu. This pulls your edits into AMP’s own tracked settings.
Note: AMP’s config sync is one-way — GUI/internal store → file. If you hand-edit the cfg and start the instance without importing first, AMP can overwrite your edits with its own stale defaults on launch. Always import before your first real start.
7. Start the server
Once everything’s copied, edited, and imported, start the instance for the first time.
Once up and running. Log into your world. and ensure everything you created or setup on it. is working through the amp instance.