Skip to content
Skip past navigation

Gaming & Esports · Registration

Tournament / LAN Registration

Squads, platforms, ranks and team sizes — collected once, before the first match starts.

7 fields · 5 required · page mode

● Live form · Tournament / LAN Registration

01 OF 07
Tournament / LAN Registration

Question 1 of 7. Squad name. Read-only preview — nothing is recorded.

Squad name *

Straight up, so nothing here reads as a promise: the form above is real — the actual seeded FormNest template, rendering live, which you can fill in. The gamer-specific questions in it are captured with standard text, dropdown and multi-select fields today; the purpose-built field types described below are not built yet. This page's neon treatment is a mock made for the web page, not a theme you can pick in the product.

What it asks

Every field, exactly as it ships.

This list is generated from the template’s own schema — the same data the form above renders from. If a question is listed here, the form asks it; if it is not, it does not.

  • Squad nameRequired

    Short text

  • Player nameRequired

    Short text

  • Gamer tagRequired

    Short text

  • PlatformRequired

    Dropdown · 4 options

    • PC
    • Console
    • Mobile
    • Other
  • Rank / tierOptional

    Dropdown · 5 options

    • Bronze
    • Silver
    • Gold
    • Platinum
    • Diamond
  • Discord handleOptional

    Short text

  • Team sizeRequired

    Dropdown · 4 options

    • Solo
    • Duo
    • Squad of 4
    • Squad of 5+

Who it’s for

Built for the people running the thing.

Organisers running a bracket, a ladder, or a LAN night who need every entrant's details in one place before seeding begins.

  • Tournament and league organisers taking squad entries
  • LAN and community events that need a roster before the doors open
  • Anyone who has run sign-ups through a chat thread and regretted it

On the workbench

Purpose-built for the scene — soon.

This part is the plan, not the product. Today this form captures everything below with standard fields; the next phase turns the gamer-specific ones into field types that understand what they hold.

  • Gamer tagA dedicated gamer tag field will become a purpose-built handle field — format-aware, with the platform it belongs to attached — instead of the plain text box capturing it today.
  • Rank / tierA dedicated rank / tier field will ship as a native tier selector with the ladder built in, so seeding and brackets can read rank directly rather than from a free dropdown.
  • PlatformA dedicated platform field will grow into a first-class platform picker that downstream logic understands, driving cross-play rules without hand-wiring every condition.
  • Discord handleA dedicated discord handle field will validate as its own field type rather than plain text, so a roster arrives with every handle in a consistent, checkable shape instead of needing a tidy-up pass before check-in.

Every line above is future tense on purpose: none of these purpose-built types is live yet. When one ships, it moves up to the live form — and this list gets shorter.