# CS2 player setup for a supervised Arena match

Arrange the current session window with the operators; see the
[current session handoff](./session-plan-2026-10-23.md). The session time is not
agreed yet; the earlier October 23 proposal was never activated. Old schedules
and room IDs have expired.
Allow 60–90 minutes for the overall acceptance session.
Each Arena room/allocation has a separate maximum one-hour expiry, so create it
after preparation and use a fresh room if needed.

## Each rostered player prepares their own account

1. Have CS2 installed and updated. Use your own Steam account and machine.
2. Sign in to [My Arena](https://hybrid-arena.com/account) with your Hybrid-ID.
   If you cannot create or access an account, arrange access with the Identity
   operator before the session. Do not borrow another person's login.
3. Set a public Arena alias in My Arena. An alias is required for CS2 seat consent.
4. Link the same Steam account in [Hybrid-ID Linked accounts](https://hybrid-id.com/account/linked-accounts).
5. Back in [My Arena's Steam card](https://hybrid-arena.com/account#steam), choose
   **Allow Arena to read Steam**. Use the same Hybrid-ID account through consent.
   Refresh and confirm the private Steam account is the one you will use in CS2.
   Ordinary Arena sign-in alone does not grant Steam access.
6. Shortly before enrollment, confirm the Steam card still shows current access.
   Renew permission if Arena requests it. Saved approval may restore access on
   returning sign-in; explicit revocation or an expired session still requires action.
7. When the Arena operator opens the reviewed staging room, visit
   [Games → CS2 match rooms](https://hybrid-arena.com/games/cs2).
   Confirm the assigned team. This separately permits private match-roster sharing
   with the named provider. Do not change teams without coordinating with the operator.
8. For the full three-player acceptance track, **wait for the outsider test to pass
   before entering the game**. A two-player gameplay check leaves that case
   `not_run`. Once the provider confirms the server, use the room's join action,
   then **Open in Steam** or the private console command. The server confirms
   identity, admission, and team.
9. After the final roster is frozen, select **I'm ready in Arena**. Every human on
   both teams must do this for the current room revision. Readiness lasts at most
   60 minutes, capped by room closure and access expiry. Roster changes invalidate it; refresh the room before declaring
   it again. This is separate from being connected and ready inside CS2.

If Steam permission expires, repeat step 5 and use **Renew permission for your
team** in the locked room. This preserves the existing Steam account/team; it
cannot change a locked roster. Reconfirm readiness after a permission renewal.
Logging out or switching Arena sessions requires current permission again.

No wallet, funding, purchase, KYC, public Steam receipt, NFT, or bet is required.
Steam IDs, game addresses and account screenshots stay in the private operator
channel. Public link verification in Explorer is optional and does not replace
private Steam consent for the roster.

## Choose the session track

**Two players can run a real gameplay check**: admission, teams, reconnect,
readiness, manual start, live telemetry and final scores. This is useful progress
but does not complete provider acceptance.

**Three players can run the full acceptance track**, including outsider rejection
and warmup replacement/removal.

The current native Arena flow requires **at least two consented humans, one on
each team, before it can allocate a game**. Therefore, an outsider-first test
needs **a third distinct Steam account**, controlled by its owner, absent from
that first roster. Two people/accounts alone cannot satisfy all three roles.
The outsider can set up Hybrid-ID/Steam access in advance but must not enroll
in the initial room. Reading Steam permission alone does not add them to a roster.

Use players A and B for the initial roster, and C as the outsider. C attempts to
join before A or B; stop if rejection fails. A and B then join. For warmup
replacement, the operator reopens the room, B withdraws, and C explicitly chooses
B's team. After Arena freezes and sends roster version 2, Raif verifies B is
kicked/rejected and C can join. Keep A and C for reconnect, readiness and the match.
This needs three accounts/participants, with B available for the removal check.
If a third account is unavailable, keep these cases not_run and reschedule;
do not fabricate consent, silently add bots, or claim the complete run passed.

## Operator preparation and boundaries

- Reconfirm source/provider key validity for the actual session. The previous
  staging window expired. Coordinate a new narrow window privately; do not
  treat an old scope or room as current.
- For the first real game, select **Duel → Short → Dust II → Europe**:
  `cs2_1v1_mr5_bo1_v1`, up to 10 regulation rounds, first to 6, overtime enabled.
  Choose a 60-minute enrollment window and create the room when players are ready;
  its deadline starts at creation.
- Current staging bindings also allow Duel 16/24 rounds on Dust II, Competitive
  16/24 on Dust II, and Wingman 10/16 on Inferno, all in `eu`. Confirm provider
  deployment and map support before choosing a different preset. Quick remains
  unavailable until provider deployment, native game validation and explicit
  map-level activation; its UI alone is not evidence of support.
- Gate changes, room creation and provider dispatch are separate supervised steps.
  This guide does not activate enrollment, create a paid server, or start a match.
- Arena accepts the dynamic game address from the authenticated, bound provider
  allocation after roster, access and address checks. No manual per-host allowlist
  edit is required. The outsider uses the privately shared operator address; Arena
  does not disclose connection details to nonroster users.
- The Arena operator's `scripts/cs2-warmup.mjs` can inspect a room, reopen its
  current warmup revision and queue the next consented roster. It never supplies
  player identities or dispatches provider requests itself. Existing dispatch
  configuration controls queued command execution. See the source runbook
  `docs/cs2-warmup-roster.md` for invocation and safety checks.
- A withdrawal or prepared roster is not proof of a kick. Observe the actual
  server after the provider confirms replacement. Unknown outcomes retain their
  original request IDs; never create a second command to bypass uncertainty.

Follow the [joint acceptance checklist](./joint-acceptance.md) and preserve
separate failed/not_run results. A `ready` response is never a live-match event.
Real players, bound source callbacks, enforcement and final results still require
joint evidence. Trading, funding, liquidity and CS2 market activation remain off.

Operators: see the [current Arena readiness runbook](https://github.com/Hybrid-Chain/hybrid-arena-website/blob/main/docs/cs2-real-match-readiness-2026-10-22.md) and [Raif’s merge-to-match checklist](https://github.com/raifemre/cs2-matchhost/blob/feat/arena-telemetry-v1/docs/partners/arena-telemetry-merge-to-match.md).
