Builds the ip:port string and the official server-browser path; this title uses EOS, so no steam:// link is generated
EOS sessions · 12 keys / 2 ini files
Two-INI Generator · Voyagers of Nera
Nautical co-op survival (Early Access) · Survival / Sailing / Co-op
Player tools indexed: 5
Admin consoles: 8
12 keys across two files and two sections, each carrying the official Allowed Values; full file and diff share one source; paste preflight included
Player tools (5)
Instant interactive calculations and recipe plannersFive branches, each anchored to the official troubleshooting section: timeout, self-connect on the same IP, fails to start, version mismatch, LAN-only
The official hosting doc, the official wiki, AMP and the egg; states plainly what could not be verified
buildid timelines for three branches, the same-minute cross-check against 0.16.15.48136 with the downgrade reason, and announcements classified by content type
Relative projection from the three official multipliers; the baseline is a measured value you enter, since upstream publishes no absolute numbers
Server admin and config generation (8)
Config files, startup scripts and command wizards for running a serverPlayer cap 10 (four sources agree); memory and disk are editable measured values, upstream exposes no requirement field
The beacon port is derived from the game port (+1); multi-instance step must be >= 2 with collision detection
Four platforms; two UDP rules by default, with TCP and the 7777-7790 range as explicit opt-ins carrying their evidence grade
The official verbatim anonymous login, component appid 1007, three runtime forms and the save-directory writability check
The exact meaning of the two official switches across three upstream forms; EOS_OVERRIDE_HOST_IP is emitted only as an environment variable
12 keys across two files and two sections, each carrying the official Allowed Values; full file and diff share one source; paste preflight included
AMP Proton GE and the egg Wine setups side by side, with the EOS root-certificate warning
No RCON (TailLogFile), two ready signals, two shutdown readings and the official log-cleanup advice
Voyagers of Nera Ports & Protocols
| Port | Protocol | Purpose |
|---|---|---|
| 7777 | UDP | Game traffic (the join port, and the port EOS advertises the session on) |
| 7778 | UDP | Beacon traffic (derived as game port + 1; both upstream sources state it as a rule) |
Voyagers of Nera Dedicated Server Install (SteamCMD)
SteamCMD appid 3937860
sudo useradd -m -s /bin/bash steam
sudo apt update && sudo apt install -y steamcmd lib32gcc-s1
sudo -u steam -i \
/usr/games/steamcmd +force_install_dir /opt/gameserver \
+login anonymous +app_update 3937860 validate +quithttps://treehousegames.notion.site/How-to-Host-Dedicated-Servers-1debc50b8edb803b9d5bd4dbfdb32c2c
Voyagers of Nera Config file paths
BoatGame/Saved/PersistedData/CustomConfig/CustomHostServerUserSettings.iniBoatGame/Saved/PersistedData/CustomConfig/CustomGameUserSettings.ini
Server notes
The server ships as a Windows binary only, and the two panels give two different Linux runtimes: AMP uses Proton GE (App.ExecutableLinux=.proton/proton, fetched from GloriousEggroll/proton-ge-custom, with releases from 11.4 upward carrying a -x86_64 suffix) while the egg uses Wine (WINEDEBUG=-all, plus an XVFB switch defaulting to 0). The official doc describes Windows paths only, so every Linux fact comes from panel artifacts. The official doc names two causes of a server that will not start: the host missing the Root CAs that EOS depends on (the fix is pointed at "Solution 2: Updating windows certificates" in the developer Discord FAQ, which could not be read this round, so only the pointer is registered), and a non-writable save directory at {INSTALL_DIRECTORY}/BoatGame/Saved/PersistedData. Pure LAN play is supported, but the official doc states plainly that the server needs an internet connection to start up correctly. Logs are not produced by default: -log gives console output and -LoggingInShippingEnabled=true writes log files to BoatGame/Saved/Logs; the official doc warns they get very large and recommends periodic restarts and cleanup. AMP's update flow overwrites both ini files from the factory template (OverwriteExistingFiles: true), silently reverting hand edits, so back up before changing anything. EOS_OVERRIDE_HOST_IP can only be a host/container OS environment variable — the official doc says verbatim that it "will not function if supplied as a command line argument" — and warns against using it when several servers or games share one machine, since it changes the setting for every EOS-backed game.
FAQ
- Which Voyagers of Nera server-admin tools are available?
- We list 8 tools for Voyagers of Nera: Capacity Planner, Port Map, Firewall Rules, SteamCMD Install, Startup Command & EOS Environment, Two-INI Generator, Linux Runtime (Proton GE / Wine), Admin Surface & Shutdown. All of them run straight in your browser.
- Which ports does Voyagers of Nera need open?
- Voyagers of Nera defaults to 7777/UDP, 7778/UDP. Use the actual instance configuration and allow only the listed protocols and ports. Check the host firewall, router forwarding and game visibility settings.
- How do I install a dedicated Voyagers of Nera server?
- Install it with SteamCMD — the dedicated server app id for Voyagers of Nera is 3937860, so +app_update 3937860 validate downloads or updates it. Config files usually live at BoatGame/Saved/PersistedData/CustomConfig/CustomHostServerUserSettings.ini, BoatGame/Saved/PersistedData/CustomConfig/CustomGameUserSettings.ini.
- Do these tools cost anything or need installing?
- No. Everything runs in the page: no install, no sign-up, no cost. Enter your values and the result appears instantly, and you can copy the generated configs and commands with one click.