Go Agent setup guide

The Go Agent runs on a machine that can reach your game server, fetches processing requests from Moneta, and sends commands through RCON. One Agent can serve several destinations. Discord-only products do not need it.

Installation requirements

The configured ZIP available in the dashboard is for Windows 64-bit. Prepare the game's RCON port and password and check the game and plugin requirements. For another OS, contact support with your environment.

Register an Agent

Select your server, open Agent management under game connections, and choose “Register new Agent.” Use a name that identifies the installation, such as ARK production server.

Keep the registration screen open until you have configured targets and downloaded the ZIP.

Add an RCON target

Add a destination in the RCON targets section. One Agent can serve several targets.

Field	What to enter
Name	A display name identifying the server or map
Key	A destination identifier, such as `ark-island`
Game	The game you are connecting
Host	The game server address as reached from the Agent
Port	The RCON port configured on the game server
Password	The game server's RCON password

If the Agent and game run on the same Windows machine, the host is usually 127.0.0.1. Otherwise, enter an address reachable from the Agent. The player connection port and RCON port may differ.

Save and check that the target is enabled. Moneta stores RCON settings and uses changes when the next job is fetched. Changing a target does not require downloading the ZIP again.

Download and run the Agent

Choose “Download configured ZIP.”
Save the ZIP on the Windows game server and extract all files.
Open moneta-agent.exe from the extracted folder.
Return to Agent management and check that “Last seen” updates.

The ZIP includes the executable and an Agent-specific config.json. No manual configuration editing is required. Do not run the executable from inside the ZIP. An existing start-agent.bat still works, but new ZIP files do not include it.

Keep the configured ZIP private

It contains credentials. Run only one instance of the same Agent and keep the same folder and cache when restarting.

Replace lost files or rotate credentials

Open Agent details and choose “Reissue configured ZIP.” This invalidates the old authentication key. Save the new ZIP and apply its configuration to any running Agent.

After closing the registration or reissue screen, you cannot retrieve the same secret again. If the download fails, keep that screen open and retry.

Update or restart an Agent

Stop the Agent before replacing its executable. Keep the existing config.json and cache, then restart. Apply the new configuration if you reissued credentials. Do not delete state files to force a job to run again. Do not downgrade while interrupted-execution records remain.

Disabling an Agent rejects new communication but cannot stop commands already delivered. Check game state before handling jobs with an unknown result.

Configuration files

Use the Agent-specific configuration downloaded at registration. To save it separately, expand the manual configuration section and use its copy action.

Setting	Meaning
`moneta_url`	Moneta API URL provided by the setup screen
`agent_id`	ID of the registered Agent
`secret`	Authentication key issued at registration or reissue

Keep the configuration private. RCON hosts and passwords belong in Moneta's target settings; the configured ZIP does not include RCON passwords.

During normal Windows startup, the Agent looks for config.json, then config.yaml, then config.yml beside its executable. Relative cache and log paths use that same folder. Updating from the old start-agent.bat preserves the location of configuration and state files.

Set MONETA_AGENT_CONFIG to use a different configuration file. Services and scheduled tasks that set this variable retain the caller's working folder as their base. Keep the configuration setting and working folder unchanged when updating. Linux and macOS startup behavior is unchanged.

Version and logs

Open PowerShell in the extracted folder and check the binary version:

Check the version

.\moneta-agent.exe --version

By default, the Agent writes JSON logs to the startup console at info level. Check startup errors, the Agent ID, job ID, and time alongside Moneta processing history. Mask credentials and private player information before sharing logs.

If an Agent opened by double-clicking exits with an error, read the message and press Enter to close its console. Running it from an existing terminal, with redirected input/output, or with --version does not wait for keyboard input.

For a persistent log, add this logging section to the existing configuration, retaining its other fields:

Logging section

{
  "logging": {
    "level": "info",
    "format": "json",
    "output": "file",
    "file": "./agent.log"
  }
}

Use a writable location. Stop and restart the Agent after editing configuration. Monitor file size and manage log retention; this setting appends to the file.

Stop and restart

In the running console, use Ctrl+C and wait for the Agent to finish stopping. Start it again from the same extracted folder. Closing or forcibly terminating the process can interrupt a command; inspect the next startup logs if that happens.

Preserve execution state

The default cache folder contains execution records, including idempotency_cache.json and result_outbox.json. They prevent duplicate processing and preserve results waiting to be reported. They are not disposable files for recovering a failed command.

If the Agent reports that it cannot restore its cache or execution state, preserve the files and check folder permissions, disk availability, and game state. Do not delete them or start the same Agent in an empty folder. Follow delivery troubleshooting and contact support if the result is uncertain.

Once connected, continue with product setup and delivery verification.

On this page