> 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/game-flow/07-game-end-and-concession.md). # 7. Game End and Concession ## 7.1 Sixteen-Turn End 7.1.1 Each player may take up to eight turns. A turn counts even if no card is Summoned. 7.1.2 After the second player completes their eighth turn, resolve all End-of-Turn Abilities, the Trigger Queue, and pending Summon packages under Section 9.3 until no processing remains. Then the game ends. ## 7.2 Full-Arena End 7.2.1 If the Arena has no empty Space when the Active Player reaches the turn-based Summon Step, record that the Full-Arena End condition has been met. 7.2.2 Skip the turn-based Summon and the associated Snatch Check. Finish any pending Trigger Queue and Summon packages, then resolve the End Step and all resulting triggers and packages until no processing remains. The game then ends even if an End-of-Turn effect created an empty Space. 7.2.3 The Full-Arena End condition does not interrupt an Ability or Snatch Resolution. A full Arena created during an Ability is handled only when a later turn-based Summon Step begins, unless another game-end condition occurs first. ## 7.3 Determining the Winner 7.3.1 When the game ends under Section 7.1 or 7.2, calculate each player's Control Score by summing the current Point Values of the Marking Tokens on Momon that player controls on the Arena under Section 5. 7.3.2 The player with the greater Control Score wins. 7.3.3 If the Control Scores are equal, the player holding the First Player Token wins. 7.3.4 A Game Result is the result determined when a Game ends. It is either a Game Win for one player or a Game Draw when no player is determined to have won under these Comprehensive Rules. 7.3.5 The Comprehensive Rules determine the Game Result, including the Control Score result, the First Player Token tiebreak, concession, and mandatory-loop Game Draw. A Game Result does not by itself determine a Match Result or Tournament Outcome. ## 7.4 Match Result 7.4.1 A Match Result is the result recorded for a scheduled Match after applying the applicable Match structure to its Game Results and any authorized tournament procedures. 7.4.2 The Comprehensive Rules do not assign Match Results. In sanctioned play, the [Tournament Rules Guide](https://momon-wonder.gitbook.io/comprehensive-rules-1.0.0/game-flow/spaces/izQAQsAurrDxg0WIqlrH/pages/yPMeUrUHMCNzPpc2nnx0#15.5-match-result) determines how Game Results, concessions, penalties, timing procedures, and format-specific tiebreak Games produce or record a Match Result. In a Clock-Controlled Match, a gameplay win is not a Completed Game Win for timing resolution until the required clock press occurs. 7.4.3 A Game Draw remains a Game Result. It is not automatically a Match Draw, Match Win, or Match Loss unless the Tournament Rules Guide or another authorized tournament procedure expressly determines that outcome. A Game that the Tournament Rules Guide treats as unfinished at the Effective Round Deadline is not recorded as a Game Result for tournament timing, even if a gameplay win condition arose before the deadline but was not finalized by the required clock press. 7.4.4 The Procedure and Penalty Guide governs infraction classification, remedies, penalties, and authorized result corrections. It does not change the underlying Game Result unless the Tournament Rules Guide expressly authorizes a tournament result procedure. ## 7.5 Tournament Outcome 7.5.1 A Tournament Outcome is an event-level result such as standings, advancement, elimination, qualification, or final placement. It is distinct from both a Game Result and a Match Result. 7.5.2 The Comprehensive Rules do not determine Tournament Outcomes. In sanctioned play, the Tournament Rules Guide determines Match Points, standings, tiebreakers, pairings, cuts, advancement, and event completion; the Procedure and Penalty Guide governs applicable enforcement and result-correction procedures. 7.5.3 No Game Result or Match Result may be replaced by an informal agreement, forecast, random method, or other procedure that the applicable tournament documents do not authorize. ## 7.6 Concession 7.6.1 A player may concede at any time. The concession ends the game immediately and the opponent wins. 7.6.2 A concession cannot be withdrawn after it is clearly communicated. 7.6.3 Tournament policy may prohibit or penalize concession. A clearly communicated concession still produces the Game Result in rule 7.6.1; any Infraction, Penalty, Match Result, or tournament-record correction is determined by the applicable tournament rules. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://momon-wonder.gitbook.io/comprehensive-rules-1.0.0/game-flow/07-game-end-and-concession.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.