> For the complete documentation index, see [llms.txt](https://momon-wonder.gitbook.io/comprehensive-rules-1.0.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://momon-wonder.gitbook.io/comprehensive-rules-1.0.0/foundations/06-setup.md).

# 6. Setup

6.1 Each player presents a legal ten-card deck for the chosen format.

6.2 Each player places all ten cards into their Hand. No card begins in a Void or on the Arena unless the applicable Tournament Rules Guide or Format Appendix expressly authorizes an Event Fact Sheet to use a different setup procedure.

6.3 Place the empty 4 × 4 Arena between the players. Establish its coordinates under [Section 4.3](/comprehensive-rules-1.0.0/foundations/04-zones-information-and-arena-geometry.md).

6.4 Establish a separate Void for each player.

6.5 Prepare the First Player Token, a shared supply of sixteen two-sided Marking Tokens or functional equivalents, and a separate supply of Ward Tokens or clear functional equivalents. A physical token supply must not limit a legal game action.

6.6 Determine the First Player by a fair random method that both players can verify, or by the applicable tournament procedure.

6.7 Give the First Player Token to the First Player. The holder takes the first turn.

6.8 Changing who holds the First Player Token during a game changes only the tiebreaker unless an effect explicitly changes turn order.

## 6.9 Start-of-Game Procedure

6.9.1 After the First Player Token is assigned under [rule 6.7](/comprehensive-rules-1.0.0/foundations/06-setup.md), the Setup Procedure is complete and the Start-of-Game Procedure begins.

6.9.2 The Start-of-Game event occurs once, immediately after Setup and before the first Turn Start event. It is not a turn and does not create a Summon or Snatch Check.

6.9.3 Abilities that trigger from the Start-of-Game event wait until the event has finished. Perform State-Based Conditions, place those waiting triggers into the Trigger Queue in event order under [Section 11](/comprehensive-rules-1.0.0/abilities-and-game-state/11-abilities-trigger-queue-and-continuous-effects.md), and resolve the Queue until it is empty.

6.9.4 If a Start-of-Game Ability changes the First Player Token, that change affects the tiebreaker unless the Ability explicitly changes turn order. The player who is the First Player under [rule 6.7](/comprehensive-rules-1.0.0/foundations/06-setup.md) remains the player taking the first turn unless an effect explicitly changes turn order.

## 6.10 First Turn Start

6.10.1 After the Start-of-Game Trigger Queue is empty, the First Player becomes the Active Player and the first Turn Start event occurs.

6.10.2 Resolve the first Turn Start using the same procedure as every later Turn Start: apply start-of-turn expirations, perform State-Based Conditions, place waiting triggers into the Trigger Queue, and resolve the Queue before Step 1 begins.

6.10.3 The first turn then proceeds through Step 1, Step 2, and Step 3 under [Section 8](/comprehensive-rules-1.0.0/game-flow/08-turn-structure.md). No additional setup action occurs between the first Turn Start event and Step 1.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://momon-wonder.gitbook.io/comprehensive-rules-1.0.0/foundations/06-setup.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.