jcreek/CosmicClash
1
0
Fork 0
mirror of https://github.com/jcreek/CosmicClash.git synced 2026-09-13 09:12:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix(multiplayer): correct allocated fleet entrypoint

Browse Source
This commit is contained in:
Josh Creek
2026-09-01 17:47:15 +01:00
parent 6042c3b154
commit 8129bb2571
4 changed files with 15 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
multiplayer-next.md
+7
View File
@@ -1393,6 +1393,13 @@ godot --path Game -- --connect 127.0.0.1:27015 --name Alice
The current working implementation now wires `deploy/k8s/base/fleet.yaml` to the digest-pinned `game-server` supervisor target, the in-cluster control-plane Service, workload roster materialization, signing/drain secret references, downward-API server/image identity, and the required game-server egress policy. `kubectl kustomize deploy/k8s/base` and `server/security/test_fleet_manifests.py` pass. The older 8.28 narrative above still records the pre-wiring state; live Agones, operator secret/image replacement, and real cluster readiness remain explicit gates.
An adversarial Fleet-entrypoint review found that the supervisor invocation had
no executable after `--`, and that its required supervisor-level protocol flag
was missing. The Fleet now passes the exported Godot server explicitly and
sets `--protocol-version=1`; the NA overlay's positional patch and manifest
regression test were updated together. This is a local launch-contract fix,
not evidence of live Agones readiness.
The NA overlay now also patches the allocated child’s `--region=NA` argument, keeping it aligned with the NA Fleet label; rendered EU and NA overlays and the adversarial manifest test verify that regional assignment validation cannot silently remain EU in the NA deployment.
Allocated Godot startup now derives its `min-players` floor from the verified signed roster size, preventing the direct-server default of one player from starting a partially admitted allocated match. A focused regression test covers six-player, casual two-player, and direct-server behavior; the full Godot harness is currently unavailable because Godot cannot open its shared `user://` log and crashes in the macOS renderer before test execution.