Appearance
Server control and console
The ACP does not directly spawn a process in the browser. Its authenticated Next.js endpoints call the private agent, which owns the game process on the host.
Start the game
Open Operations → Server Control and use Start with Lead level or above. The agent must be running with the correct SAMP_DIR, binary and shared key. Stop any separately started game first; the agent cannot adopt it.
Read the status and log output after starting. A brief “started” response is not proof the game stayed alive. Database or ColAndreas initialization can stop it during startup.
Stop the game
Stop requires Manager level or above. Save/settle work through your normal maintenance procedure, then request a clean stop. With configured RCON, the agent attempts RCON exit; otherwise it writes exit to its owned PTY. A fallback can terminate a process that fails to exit.
Do not repeatedly click Start while a shutdown is still in progress. Confirm the old process has exited before starting another instance.
Scheduled start
The web app can schedule a start, not a complete durable recurring restart plan. Its timer is stored in the web process’s memory. Redeploying/restarting the web app loses that timer. Multiple web replicas would not share one authoritative scheduler.
Use your host’s scheduling/operational system for durable scheduling, while preserving a single owner for the game. Do not assume an ACP scheduled start restores a game after every host reboot.
Developer console
Console commands and streaming require Developer level. Keep RCON credentials and the agent key server-side. Use trusted engine commands and check the output. A raw console can alter or stop the server; it is not an ordinary player support tool.
The agent reads log.txt and process output. Configure engine logging consistently if you change the filename. ACP log tables are a separate audit source and are not the same as this console stream.
Maintenance
Use the supplied maintenance tools and a planned service lifecycle. The game’s script-side SERVER_PASSWORD, engine RCON password, player passwords and agent key serve different purposes. Match only the settings that actually need to match; never reuse one secret for everything.
If status looks wrong
| Symptom | Check |
|---|---|
agent_unreachable | Agent process, URL, private network and port |
| Forbidden | Current account rank and operation-specific requirement |
| Stopped but players are online | An independent game process may own the port |
| Starts then exits | Game log.txt, MySQL, plugins, collision file and permissions |
| No console stream | Developer access, agent connection and logging file |
See the agent setup before changing process-control code.