Vi-Fighter Session Fleet
Ask for a dedicated session, join it from a terminal
GoKubernetesK3sSSEMultiplayerNodePort
Fleet
This page needs JavaScript: it talks to the session API and streams log records over the same origin.
The page script did not load, so nothing here is live. Reload the page; if it persists, the console will name the reason.
One request, one container. The allocator waits for the pod, its endpoint and the game itself before it answers, so this can take up to about a minute.
No session selected. Request one, or pick a running session below.
Session
—Reading the fleet…
How it works
- Request
- The button posts an empty object to the session API. One Job and one owned Service are created, and the response arrives only once the pod, its endpoint and the game itself are ready — there is no second readiness check to wait through.
- Scenario
- The list is what the node serves right now: the allocator reads its scenario volume on every request, so it can change while this page is open. Leaving it on the deployment default takes the deployment's own scenario.
- Join
- The join target is a raw TCP address for
vif -join. It does not pass through the web server and is unaffected by anything on this page. - First join
- A 90-second window starts the moment the session is handed over. Nobody arriving in it ends the session, and the slot returns to the fleet.
- Ending
- A session ends itself when its roster empties for the grace period. There is no delete button here on purpose: an anonymous caller must not be able to end somebody else's game.
- When the fleet is full
- Ten concurrent sessions is the ceiling, enforced by a cluster quota rather than by this page. A full fleet is answered with a retry delay, which the page waits out rather than retrying immediately.
- Logs
- The record stream is a separate route and fails on its own. If it is down the fleet summary and the game keep working; the panel says so rather than implying an outage.
Session log
Every running session's records, live over the same origin. Filter to one session to follow it alone. The stream and the fleet summary fail independently.
Connecting…