Back to landing page

Beta Battle Path

Open the play launch first.
Load the console only when needed.

`/play` is now the launch surface for the beta route. Use it to resolve the next sanctioned step, then move into `/play/console` only when you need the heavy interactive battle surface. The long-form combat playbook remains on its own route.

training groundnpc encountersranked duelpeer duelwallet custody

Live next step

Loading your next beta step

The battle shell is still syncing your journey, deck, and room state.

Statussyncing player route

Session order

1

Account and custody

Use a real player session before linking wallets, testing custody handoffs, or validating live battle authority.

2

Deck and hero setup

Choose a hero, save a 7-card deck, and confirm any trance or cosmetic variants before opening a battle room.

3

Battle proving path

Start with training ground, move into NPC encounters, then validate ranked and peer duel flows after the first two are stable.

4

Engine notes and diagnostics

Use the separate playbook route when you need fixture reports, stack notes, and the long-form engine checklist.

Route split

Launch, console,
and playbook are separate now.

Use `/play` for the fastest route selection path, `/play/console` for the live battle surface, and `/playbook` for deterministic replay notes and engine planning. That keeps each surface aligned with its actual startup cost.