From 65cbb8cfd4ccc66c32ec7efdc86838af1535e61d Mon Sep 17 00:00:00 2001 From: Greg Date: Sun, 25 Oct 2026 02:35:52 -0400 Subject: [PATCH] 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 --- games/ark-survival-ascended-crossplay/game.yaml | 1 + games/ark-survival-ascended-crossplay/test.yaml | 6 +++--- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/games/ark-survival-ascended-crossplay/game.yaml b/games/ark-survival-ascended-crossplay/game.yaml index 59809ad..460f979 100644 --- a/games/ark-survival-ascended-crossplay/game.yaml +++ b/games/ark-survival-ascended-crossplay/game.yaml @@ -325,6 +325,7 @@ agnosticCommandConfig: restPortKey: null restUser: null logFilePath: ShooterGame/Saved/Logs/ShooterGame.log +readyPattern: Server has completed startup and is now advertising for join backupPaths: - ShooterGame/Saved maxBackupSizeMb: 4096 diff --git a/games/ark-survival-ascended-crossplay/test.yaml b/games/ark-survival-ascended-crossplay/test.yaml index f3ff373..5ce4a54 100644 --- a/games/ark-survival-ascended-crossplay/test.yaml +++ b/games/ark-survival-ascended-crossplay/test.yaml @@ -1,6 +1,6 @@ # yaml-language-server: $schema=../../schema/test.schema.json # Values CI uses to boot-test this game. Never put real credentials here: map them under 'secrets'. -# No readyPattern yet: the server must stay up for 10 minutes, which covers the ~13 GB first -# download and Proton's slow first start. -settleSec: 600 +# Ready means advertising for join, which comes about 2 minutes after "Full Startup"; the first boot also +# installs ~13 GB and Proton, so the timeout is generous. +readyExample: '[2026.10.25-06.32.24:246][239]Server has completed startup and is now advertising for join. (9.96GB Mem)' timeoutSec: 2400