# Formant & Rules

### Available Formats:

* Singles 6v6: 1 Pokémon active per side, bring up to 6.
* Doubles (VGC-style): 2 Pokémon active per side at once, bring up to 4 (typical VGC rules; the config enables up to 6).
* Randoms: the server generates a full team for each player (respecting bans/clauses); players don’t use their stored/current parties.
* Custom: using the defined syntax, make as many formats as you want, with custom rules, level caps, and minimum players for each one!

### Bracket type

* Single-elimination bracket.
* BYE slots can exist if the player count is not a power of two. A BYE means a participant automatically advances to the next round without battling.

### Team sources

Players can register using:

* Current party
* Saved party slots (up to 3 per player)
* Showdown/PokePaste import (supports nicknames, shinies, regional forms like `galarian=true`, and move/item/ability parsing)
* Randoms (server-generated team; still respects bans/clauses)

### Validation timing

Team validation occurs before a player is accepted into the tournament (levels, banned species/items/abilities/moves, and enabled clauses). If multiple problems exist, the rejection message lists them all.

### Move timer

If enabled, a per-turn move timer runs; if the active player does not act in time, they forfeit.

### Gimmicks

Formats can toggle gimmicks such as Mega/Tera/Z/Dynamax. When disabled, the mod blocks use during the tournament match.


---

# Agent Instructions: 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:

```
GET https://dawnshade.gitbook.io/dawnshade-docs/docs/dawn-tournaments/summary/formant-and-rules.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.