Updating Changes To Your Server

Overview

After you change any core settings (e.g., scenario, ports, player limits, mods, admin passwords) via the Sammys Servers panel (which uses Pterodactyl under the hood), those edits won’t take effect on the live Arma Reforger instance until you restart the server through the Sammys Servers interface. This article explains why a restart is necessary, which panel‐driven changes trigger it, and provides step‐by‐step instructions for performing that restart.

Why a Restart Is Required

• Configuration Reload: The Arma Reforger server binary reads its config.json (and other in-container files) only at launch. Any edits—whether to scenarioId, playerCountLimit, gameProperties, or "mods"—must be reloaded by restarting the process.

• Port and Network Binding: Ports are locked to your server.

• Admin/Player Credentials: Updates to adminPassword, password, or entries in the "admins" array only apply when the server initializes.

• Mod/Scenario Activation: Enabling or disabling mods (workshop) requires the engine to load those assets at boot—hot-reload isn’t supported for Arma Reforger.

• Engine/Plugin Updates: Replacing or updating the server binary (for example, via SteamCMD invoked outside Sammys Servers) requires a fresh process to load the new executable.

Note: Cosmetic edits to Sammys Servers’ appearance or user-facing UI do not require a server restart—only changes that affect the running game binary or its configuration.

 

Which Panel Changes Require a Restart

Any of the following actions performed via Sammys Servers will necessitate restarting the Arma Reforger instance:

1. config.json Modifications (Core Settings)

   • Changing server name, server password, or admin password

   • Adjusting scenarioId (e.g., switching from Conflict → Game Master)

   • Editing playerCountLimit, visible, or crossPlatform

   • Tweaking values under "gameProperties" (e.g., maxViewDistance, battleEye, fastValidation)

   • Modifying the "mods" array (adding/removing workshop IDs or custom PBOs)

2. Port/Network Settings

   • Changing gameHostBindPort or gameHostBindAddress

   • Changing gameHostRegisterPort or gameHostRegisterBindAddress

   • Any A2S query port adjustments (if defined under "a2s")

3. Authentication Settings

   • Updating adminPassword or entries in the "admins" array

   • Modifying any user-level "password" fields

4. Server Binary/Engine Updates

   • Uploading or replacing ArmaReforgerServer binary inside the server’s folder via Sammys Servers file manager or SFTP

   • Applying a new Windows EXE or Linux binary by external means

5. Mod/Asset Deployment

   • Uploading/deleting .pbo files or workshop mods into the Mods folder via Sammys Servers file manager

   • Changing scenario packages (e.g., swapping mission .conf files)