PAM Getting Started
From an empty ship to a working mining job in a few minutes — all through chat.
!pam chat commands on the server. Sit in your ship, use the commands, and the Torch plugin does the flying. PAM answers as Commander PAM.
"Thorium Test" is a saved job; "Miner Test" is a profile; "Sens Miner" is the ship's grid name; "sens station" is the station's grid name. For every example with each argument labelled, see PAM Workflow.
🧩 The four things, and how they connect
These are four different names. They are not interchangeable, and they point at each other in a fixed way:
| Name in this example | What it is | What it holds |
|---|---|---|
| Sens Miner | The ship (grid) | Drills, connector, thrusters, AI blocks. |
| Thorium Test | The saved job | Where and what: the GPS and the ore. |
| Miner Test | The profile | How: role, cargo, station, connector, speeds, return rules. |
| sens station | The station grid | Connectors, cargo, power. |
How they connect:
- The station is set on the profile, not on the job or the ship.
- The connector is also set on the profile.
- The profile is not attached to a job made with
!pam job new. Name the profile when starting:!pam start "<job>" "<profile>" "<grid>". - The job is started on the ship, with the profile: job + profile + ship.
!pam job new "Thorium Test" "GPS:thor:35875.86:12311.12:26887.91:" Thorium
job "Thorium Test" · where: that GPS · what: Thorium
!pam profile new "Miner Test"
profile "Miner Test"
!pam profile set "Miner Test" station "sens station"
profile "Miner Test" → station "sens station"
!pam profile set "Miner Test" dock any
profile "Miner Test" → any free connector
!pam start "Thorium Test" "Miner Test" "Sens Miner"
job "Thorium Test" + profile "Miner Test" + ship "Sens Miner"
The last line is the one that starts it: job, then profile, then ship.
Other examples on this page use different names — “Thorium Test” is a job, “Miner Test” is a profile, and “Sens Miner” is a ship. They play the same three roles as the names above.
!pam profile set "Sens Miner" ... fails because Sens Miner is the ship. !pam profile set "Thorium Test" ... fails because Thorium Test is the job. !pam job new "Miner Test" "Sens Miner" fails because the second value must be a GPS, not a ship name.
🚀 Five steps to your first job
!pam start "GPS:My Rock:1000:2000:3000:" iron,nickel. To use a profile, save the job first and start it with the profile: !pam start "Thorium Test" "Miner Test" "Sens Miner".!pam status. Stop with !pam stop, send it home with !pam home.🧭 Jobs and profiles are not the same thing
Most confusion comes from mixing these up:
| Thing | What it holds |
|---|---|
| Saved job | Where and what: the GPS, the ores, a shuttle route, or a patrol/escort objective. |
| Profile | How the ship works: role, speeds, cargo limit, station, which connector, return rules and AI profile. |
Universal form: !pam start <job> <profile> <grid>. The job says where/what; the profile says how; the grid says which ship.
!pam job new "Thorium Test" "GPS:thor:35875.86:12311.12:26887.91:" Thorium
Saved Thorium Test.
!pam start "Thorium Test" "Miner Test" "Sens Miner"
Starts the saved job on Sens Miner with the Miner Test profile.
Read it as: start what (the job) with how (the profile) on which ship.
🏗️ A miner that docks by itself — exact commands
This makes a miner fill to 90%, fly to your station, unload, recharge, undock and go back to the same rock. Do it once, then reuse the profile and job.
"Thorium Test" = the saved job; "Miner Test" = the profile; "Sens Miner" = the ship's grid name; "sens station" = the station grid name; "PAM Dock 1" / "PAM Dock 2" = connector names.
Universal form:
!pam profile set <profile> station <station grid>
!pam profile set <profile> dock <connectors|any|none>
!pam job new <job> <gps> [ores]
!pam start <job> <profile> <grid>
Angle brackets are placeholders. Quote a name with spaces; a GPS is always quoted.
!pam stations1. Find the station and connectorsLists every grid you can dock at, and its connectors. The grid name is what goes in the profile. A connector marked (in use) is busy; (ship) after a grid name means the station is a moving ship.
sens station: PAM Dock 1, PAM Dock 2 (in use)!pam profile new "Miner Test"2. Make a profileA blank profile that you can change without affecting the built-in Miner profile.
!pam profile set "Miner Test" role minerMining role.
!pam profile set "Miner Test" cargo 90Leave the rock at 90% cargo. The default is 95%.
!pam profile set "Miner Test" station "sens station"3. Set the stationUse the exact grid name from !pam stations, not the connector name. Use none to clear it.
!pam profile set "Miner Test" dock any4. Choose connectorsUse any free connector of the right size. To pin one or more, give their names in quotes: !pam profile set "Miner Test" dock "PAM Dock 1,PAM Dock 2". none goes back to any.
!pam job new "Thorium Test" "GPS:thor:35875.86:12311.12:26887.91:" Thorium5. Save the jobThe GPS and the ore. A GPS start cannot take a profile, so save the job first.
!pam start "Thorium Test" "Miner Test" "Sens Miner"6. Start itStarts the saved job on the named ship with the named profile.
!pam home, empty it, then !pam resume.
🔌 Which connector does PAM use?
| Profile setting | Behaviour |
|---|---|
dock any (default) | The nearest free connector of the right size. If any station connector has [PAM] in its name, PAM uses only those [PAM] connectors. |
dock "Dock One,Dock Two" | Only those named connectors, in any order. Names must match !pam stations; comma-separated, inside quotes. |
dock none | Clears the list and goes back to any free connector. |
- Size matters. A small ship cannot use a large connector, and a large ship cannot use a small one. If your ships are different sizes, make one profile for each size with different connector names.
- Conveyors matter. The ship's connector must have a conveyor path to the cargo containers it is filling or emptying, and to the tanks/batteries for charging.
- Busy docks. PAM queues for a free connector.
!pam stationsshows (in use); PAM does not take a dock another ship is using. - Names. Use the connector name as shown, without the (in use) note.
- Station owners: put
[PAM]in the names of the connectors you want PAM ships to use. That keeps players' ships away from your other docks.
🛡️ Warships: escort groups and “mayday”
How to start the group
For this example: profile "Guard"; escort job "Guard Duty"; miner grid "Sens Miner"; warship grids "Warship One" and "Warship Two".
Syntax:
!pam profile set <profile> role escort
!pam job escort <job> <guarded grid>
!pam group <job> <profile> "<grid one,grid two>"
The escort job needs a valid GPS only because every saved job needs one; the Escort role uses the guarded ship, not that GPS. The simplest GPS is the miner's position, which you can add with !pam gps "Sens Miner".
!pam profile new "Guard"
!pam profile set "Guard" role escort
!pam profile set "Guard" manoeuvrespeed 30
!pam job new "Guard Duty" "GPS:Sens Miner:1000:2000:3000:"
!pam job escort "Guard Duty" "Sens Miner"
!pam group "Guard Duty" "Guard" "Warship One,Warship Two"
!pam group starts the saved job on several ships. With an Escort job, each ship takes a place in the ring around Sens Miner. Set the warships' AI blocks in the ship's control panel; PAM leaves them as set, and there is no chat command for AI settings.
Patrol
A patrol needs two or more GPS points. !pam job new saves one GPS, and there is no chat command to add more, so a Torch-only patrol is limited to what the saved job already holds. Start it with !pam start "<job>" "<patrol profile>" "<grid>". The ship flies between the points; its AI blocks fight anything that comes into range.
Battleship or fighter at a point
Set role battleship or role fighter, give it an AI profile, save a job at the GPS where it should wait, and start it. It holds that area and fights with its AI blocks. To defend a miner, put the warships on an Escort group; there is no broadcast mayday.
✅ Ship checklist
A mining ship needs:
| Requirement | Why / notes |
|---|---|
| Drills facing one way, with no gap | PAM plans straight tunnels around the drill shape. |
| The hull must fit the hole the drills cut | If the hull is wider than the combined drill cut, it will scrape the tunnel walls. Add drills across the hull or use a narrower ship. |
| A connector | For docking at your station and unloading. |
| Thrusters in every direction + at least one gyro | PAM flies the ship directly; it needs full control. |
| Stored power and cargo space | Batteries for the trip; cargo under 95% full. |
| Not docked; landing gear unlocked | A docked ship is not under PAM's control. |
| Remote Control autopilot off | Two flight controllers would fight each other. |
| Within 5 km of the asteroid | A jump drive can cover more, if Use jumps is on in the profile. |
| GPS within 200 m of the rock | PAM needs to find the asteroid from the GPS. |
| Ore detector (optional) | Not needed to mine: PAM's job scan reads the asteroid directly. A working detector is only needed for Log ores and Return on ore, and its range sets how far those look. |
| Asteroid only | Planet mining is not supported yet. |
PAM checks these when the job starts. If something is missing, the chat reply says what.
⌨️ Start, stop and control
Universal forms:
!pam start <job> <profile> <grid>
!pam start <gps> [ores] [grid]
!pam stop [<grid>]
!pam resume [<grid>]
!pam home [<grid>]
Angle brackets are placeholders; quote names with spaces. The start order is job, profile, grid.
!pam start "GPS:Name:X:Y:Z:" [ores] [grid]
Start
Mines at a GPS. Leave the ores out for the whole asteroid. Sit in the ship to skip the ship name.
!pam start "GPS:Nickel rock:1000:2000:3000:" nickel
Starts a job called “Job on …” at that rock.
!pam start "<job name>" [profile] [grid]
Saved job
Starts one of your saved jobs, with the named profile if you give one.
!pam group "<job name>" <profile> "<grid one,grid two>"
Several ships
Starts a saved job on several ships. Each ship gets its own place and tunnels. The profile is required.
!pam status [grid]
Status
Shows the ship's job, cargo, power and health. This is the fastest way to see what it is doing.
!pam stop [grid]
Stop
Stops the ship where it is and hands it back to you. The job ends.
!pam resume [grid]
Resume
Sends a waiting ship back to work — after a limit, at the job start, or at a dock.
!pam home [grid]
Home
Stops drilling, backs out of the tunnel, and returns to the job start or to its station.
🏗️ With a station
For this example: profile "Miner Test"; station "sens station"; ship grid "Sens Miner".
Syntax:
!pam profile set <profile> station <station grid>
!pam profile set <profile> dock <connectors|any|none>
!pam start <job> <profile> <grid>
Set the station in the ship's profile, and PAM docks, unloads, charges to 95%, and goes back to work by itself.
!pam profile set "<profile>" station "<station name>"
Station
Use the exact grid name of your station. Use none to clear it.
Without a station, the ship waits next to the rock at Limit reached. Bring it home, empty it, then resume.
📊 What the status means
| Status | Meaning |
|---|---|
| Scanning | PAM is scanning the asteroid before it plans tunnels. |
| Waiting for room | Other ships are working where this job could go. |
| Lining up | Moving to the start of the next tunnel. |
| Entering | Flying into the tunnel. |
| Drilling | Mining. |
| Leaving | Backing out of the tunnel, or carrying on out of an open far end and turning there. |
| Limit reached | Stopped for cargo, power, damage, or another profile limit. Fix it, then resume. |
| Returning | Flying back to the job start or station. |
| At job start | Waiting where the job began. |
| Job complete | All tunnels and pockets of ore for the job are done. |
| Blocked | Something is in the way. See Safety & Limits. |
| Paused | Lag safety or an admin stopped the ships. |