How to use Beacon to configure an Ark server?

Want fine-tuned Ark settings without wrestling .ini files? Beacon does the heavy lifting. Connect, edit, deploy. Fast and clean.

Prerequisites

• Windows PC with install rights (for the Beacon client)
• Access to your Oxygenserv panel (login and password)
• Server SFTP credentials (host, port 22, username, password)
• Ark: Survival Evolved server running on Oxygenserv
• A short maintenance window to stop/start the server safely

Detailed steps

1. Download and install Beacon
   Go to Beacon’s official website and grab the latest Windows build. Run the installer and finish the setup (Next, Next, Finish). Launch Beacon from the desktop shortcut. If Windows SmartScreen appears, click “More info” then “Run anyway”.
2. Create a new Ark project
   In Beacon, click “New Project”. Pick “Ark: Survival Evolved” and confirm with “OK”. Give your project a clear name (e.g., “Ark_Oxygenserv_Main”). You’ll land on the main screen with the left menu (Rules, Engrams, Loot, etc.).
3. Get your SFTP credentials from Oxygenserv
   Log into your Oxygenserv panel and open your Ark service. Click “Stop” to fully stop the server before editing. Go to the “Files” tab, then “SFTP Credentials” (or “SFTP”). Copy the host, port 22, username, and generated password. If you later see “Connection refused,” it’s usually a wrong port or password.
4. Connect Beacon to your server via SFTP
   Back in Beacon, click “Import” on the toolbar. Choose “Server with FTP Access,” then “Continue.” Set the mode to “SFTP.” Enter: a) Host: paste the SFTP host, b) Port: 22, c) Username/Password: from the panel. Click “Test Connection” if available, then “Continue.”
5. Import current server configuration
   Beacon will read GameUserSettings.ini and Game.ini from ShooterGame/Saved/Config/WindowsServer/. Wait for the completion prompt and click “OK.” If Beacon reports a missing file, confirm the server is stopped and the root path is correct. Your existing settings should populate the left-side sections.
6. Edit gameplay settings
   Open “Rules” and tune multipliers precisely. Concrete examples: a) XP: XPMultiplier=2.0 (in Game.ini), b) Harvest: HarvestAmountMultiplier=2.5, c) Taming: TamingSpeedMultiplier=5.0, d) Difficulty: OverrideOfficialDifficulty=5.0 to spawn higher-level dinos. Beacon writes each value into the correct file for you.
7. Customize advanced rules
   Use Beacon’s sections for PvP, Engrams, Loot, and more. Examples: enable tribe logs with MaxTribeLogs=300 in GameUserSettings.ini. For PvE, set ServerPVE=true. If you want RCON, add RCONEnabled=True and set RCONPort=27020. If Beacon shows a conflict warning, click it to see which value needs adjustment.
8. Save and review generated files
   Click “Save” to snapshot your Beacon project. Open the file preview (e.g., “View Files”) to check what will be written into GameUserSettings.ini and Game.ini. Confirm values render exactly as intended (e.g., allowThirdPersonPlayer=true). If something’s missing, go back to the relevant section and fix it.
9. Deploy changes to the server
   Click “Deploy.” Select your connected server, then “Begin.” Beacon uploads to ShooterGame/Saved/Config/WindowsServer/ and replaces old values safely. If you see “Permission denied,” reconnect SFTP and ensure the server is stopped.
10. Restart and validate in-game
    Return to the Oxygenserv panel and click “Start.” Open the “Console” and look for “Server Listening” or “Setup complete.” Join the server and verify rates (e.g., harvest a rock to confirm HarvestAmountMultiplier). If a setting didn’t apply, stop, redeploy, and start again.

Tips & optimization

– Adjust in steps: move from 1.0 to 2.0, observe economy, then iterate. This protects server balance.
– Keep backups: regularly export your Beacon project (.beacon) and download GameUserSettings.ini and Game.ini before deployment.
– Stage major changes: rates first, then engrams, then loot. Easier rollbacks and cleaner troubleshooting.
– Use Beacon Presets to standardize across main/event/test servers. Huge time-saver for future updates.
– Check coherence: very high TamingSpeedMultiplier + very low food drain can create odd behavior. Tune pairs together.

FAQ

Beacon can’t connect — what should I check?

Ensure the mode is “SFTP” (not FTP), the port is 22, and you pasted the exact username/password from the panel. If you see “Host key mismatch,” remove the old saved SFTP entry in Beacon and reconnect. Also confirm the server isn’t mid-restart.

Where are Ark config files located?

By default: ShooterGame/Saved/Config/WindowsServer/GameUserSettings.ini and ShooterGame/Saved/Config/WindowsServer/Game.ini. Beacon writes directly to these. If changes don’t show, stop the server, redeploy, then start.

How do I roll back a bad change?

Open your Beacon project, use version/history or re-import previous .ini backups if you saved them. Redeploy and restart. Pro tip: version your presets (e.g., “v1.2-rates,” “v1.3-loot”) for clear traceability.

You’ve got Beacon dialed in for Ark now. Test, tweak, and lock in stable settings. Your players will feel the difference.

Related articles

• How do I add mods to a Euro Truck Simulator 2 server?
• Optimum configuration of a Palworld server: the PalWorldSettings.ini file
• How do I connect to a 7 Days to Die server using Telnet?