fix(ark): retry the install; ready when advertising for join #3

Merged

greg merged 3 commits from fix/ark-install-retry into main 2026-10-25 15:10:18 +00:00

Conversation 2 Commits 3 Files Changed 2

+5 -4

3 Commits

Author	SHA1	Message	Date
greg	ba09fe35d7	Merge branch 'main' into fix/ark-install-retry	2026-10-25 07:09:33 +00:00
gregandClaude Opus 5.5	65cbb8cfd4	feat(ark): ready when advertising for join ... First boot with the install fix ran ARK for ~10 minutes and found, in ShooterGame.log: "Server: ... has successfully started!", "EOS ownership validation initialized: Success", "Full Startup: 36.26 seconds" and, about two minutes later, "Server has completed startup and is now advertising for join. (9.96GB Mem)". That last line is when players, console players through EOS included, can join, so it is the readyPattern; the real line is test.yaml's readyExample. Boot tests now wait for it instead of only checking ARK stays up for 10 minutes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-25 02:35:52 -04:00
gregandClaude Opus 5.5	9fef27cd40	fix(ark): retry the server install before handing over to the image ... The image's start_server runs SteamCMD once and carries on even when it fails; SteamCMD's intermittent "Missing configuration" error then left no server installed, so ARK exited and only the node's restart policy saved it (a boot test would fail on the restart). First boot showed it. The startup command now downloads SteamCMD if missing, runs the usual "+login anonymous +quit" warm-up and installs app 2430930, retrying up to three times until ArkAscendedServer.exe exists. start_server's own install step then only validates. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-25 02:25:45 -04:00