🏷️
Names used in the examples: "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; "PAM Dock 1" is a connector.

No. The Torch server plugin is installed on the server. Join, sit in a ship and use !pam chat commands.

It flies ships, scans asteroids, plans tunnels, docks, manages jobs and profiles, and answers !pam chat commands. It sees the whole world, so grids move without sync delay and jobs keep running while players are offline.

  • Type it in lower case: !pam stop, not !PAM STOP.
  • Put GPS and names with spaces in quotes.
  • Sit in the ship, or add its exact name.
  • Check that you are on the test server, and that the server plugin is running.
  • Read the reply β€” it usually says what is missing.
  • Use the right kind of name. !pam profile set takes a profile; !pam job new takes a GPS; !pam start takes a job, then optionally a profile, then a ship. A ship name is not a profile or a GPS.

Check !pam status and !pam alerts. Common reasons:

  • Limit reached β€” cargo, power, fuel, damage or a profile return rule.
  • Blocked β€” something is in the way.
  • Paused β€” lag safety or an admin hold.
  • Docking β€” waiting for a dock or unable to connect.

Fix the reason, then !pam resume. See Safety & Limits.

The server was slow, so lag safety stopped every PAM ship, or an admin paused them. They resume when sim speed recovers or the admin releases the hold. See Safety & Limits.

It reached a limit, usually full cargo. Its status is β€œLimit reached”. Bring it home with !pam home, empty it, then !pam resume.

Or set a station in the profile with !pam profile set "<profile>" station "<station name>", and it unloads and recharges by itself.

A profile is a named set of settings: role, speeds, cargo limit, station, connectors, return rules and AI profile. It answers how a ship works. A saved job answers where and what: the GPS, the ores, a shuttle route or a patrol/escort objective.

You start a saved job with a profile: !pam start "Thorium Test" "Miner Test" "Sens Miner" β€” job, then profile, then ship. Change a profile with !pam profile set "<name>" <setting> <value>.

The station and connector are set on the profile. The job only has the GPS and ore. The ship is chosen when you start. A job made with !pam job new has no attached profile, so name it on the start command.

Set a station in a profile, then start a saved job with that profile.

For this example: profile "Miner Test"; job "Thorium Test"; ship grid "Sens Miner"; station "sens station"; connector "PAM Dock 1"; ore Thorium.

Syntax:

!pam profile set <profile> station <station grid> !pam profile set <profile> dock <connectors|any|none> !pam start <job> <profile> <grid>
!pam stations sens station: PAM Dock 1, PAM Dock 2 (in use) !pam profile new "Miner Test" !pam profile set "Miner Test" role miner !pam profile set "Miner Test" cargo 90 !pam profile set "Miner Test" station "sens station" !pam profile set "Miner Test" dock any !pam job new "Thorium Test" "GPS:thor:35875.86:12311.12:26887.91:" Thorium !pam start "Thorium Test" "Miner Test" "Sens Miner"

The ship fills to 90%, docks at sens station, unloads, charges to 95%, undocks and returns to the rock. Cargo and charge trips resume by themselves.

A GPS start cannot take a profile. Save the job first with !pam job new; then start the saved job.

  • dock any (default): the nearest free connector of the right size.
  • If any connector at the station has [PAM] in its name, only those are used.
  • !pam profile set "<profile>" dock "PAM Dock 1,PAM Dock 2" pins named connectors. Names are comma-separated and must match !pam stations.
  • dock none clears the list and goes back to any free connector.

Use !pam stations to see the grid names and connector names, and which are in use. A small ship needs a small connector; a large ship needs a large one. Make one profile per ship size if needed.

You can put several warships on one miner as an Escort group. They fly in formation around that miner and their AI blocks fight enemies that come into range.

There is no mayday broadcast. The group does not wait for a distress call or jump to another ship when it is attacked; it is assigned to the miner when you start the job.

For this example: profile "Guard"; job "Guard Duty"; miner grid "Sens Miner"; warship grids "Warship One" and "Warship Two".

With chat commands, use a group start after setting the guarded ship:

!pam profile set <profile> role escort !pam job escort <job> <guarded grid> !pam group <job> <profile> "<grid one,grid two>"
!pam gps "Sens Miner" !pam profile new "Guard" !pam profile set "Guard" role escort !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"

Set each warship's AI blocks in the ship's control panel. For a patrol, the job needs at least two GPS points; !pam job new saves one, so a Torch-only patrol is limited to what the saved job already holds.

Not for mining. PAM's job scan reads the asteroid's voxels directly, so it finds the ore and plans tunnels without an ore detector. The GPS and the scan do the work.

A working ore detector is only needed for two optional settings:

  • Log ores β€” PAM logs the ore the detector sees while the ship flies between places, for the Ores list and map. Without a detector, nothing is logged.
  • Return on ore (combat roles) β€” go home when the detector finds ore. Without a detector, that condition never triggers.

The detector's range sets how far those two features look. A detector that is off, unpowered or broken counts as no detector. The main mining job is unaffected either way.

PAM checks the ship and the job. Common messages:

  • Needs drills or a connector, or the drills do not face one way.
  • The ship is docked, the landing gear is locked, or the Remote Control autopilot is on.
  • No stored power, no cargo space, or the ship is too heavy.
  • The ship is more than 5 km from the GPS, or the GPS is more than 200 m from the rock.
  • Planet mining is not supported yet.
  • A server limit: too many active ships, too many armed ships, keep-out distance, or combat roles off.

Yes. Use !pam group "<job name>" <profile> "<grid one,grid two>". Each ship gets its own place and its own tunnels.

PAM saves running jobs every 30 seconds and resumes them about 10 seconds after the world loads. A miner inside the rock backs out first, then continues the same tunnel. Finished tunnels stay finished.

Not yet. Asteroids only.

Yes, with combat roles: Battleship, Fighter, Scout, Patrol and Escort. The game's AI blocks fly and fight; PAM gives the orders. See Profiles.

A ship collects everything it drills. Turn on Clear stone to the ore in the profile to drill through stone without keeping it. It does not work for whole-asteroid jobs.

Yes, with the server plugin: max ships per player, max armed ships, keep-out distance, and combat roles on or off. These protect the server's sim speed. See Safety & Limits.

The Torch log is in <Torch folder>\Logs. For a bug report, include the last ~30 lines around the problem. For more detail, turn on Debug logging in the Commander PAM tab in Torch.

Yes. They are kept on the server, with the server plugin.

Chat-only players can share the job's name, GPS and ores, and the other player can create it with !pam job new. There is no code export in chat.

Not yet. Load balancing is planned but not built. The Torch plugin does all the work on this server.

Yes. Add saved jobs with !pam queue add "<job name>", and the ship starts each one as the last finishes. !pam queue shows what is waiting. A job that cannot start waits at the front, and the queue says why. See job queue commands.

No. Don't run the old PAM script on a ship that the plugin flies. They would fight over the ship.

πŸ›
Still stuck? Post in #pam-testing with the command you used, the exact reply, the ship or station, the time, and the relevant Torch log lines.