Event Entrants

Manage all entrants for a tournament event
TO Management Hub Authenticated
/TO/event_entrants.html

Source

  • /public_html/TO/event_entrants.html [oai_citation:0‡event_entrants.html](sediment://file_00000000f38c71f4967d8e95b84b0d20)
  • /public_html/TO/scripts/event_entrants.js [oai_citation:1‡event_entrants.js](sediment://file_00000000dfdc720a802df47c71980d8b)

Purpose

  • View all entrants in an event
  • Add registered users
  • Create/edit guest entrants
  • Trigger claim flows
  • Navigate to army management

System role

This page is the entry point for all entrant-related workflows. 
Event → Entrants → Entrant Army → Units

URL parameters

Parameter Required
event_idYes
tournament_idFallback

APIs Used

  • to/event_entrants_list.php
  • to/event_entrant_save.php
  • to/event_entrant_get.php
  • to/event_entrant_delete.php
  • to/user_search.php
  • to/event_entrant_claim_send.php

Page structure

  • Entrants list (top)
  • Registered user search
  • Guest entrant form

Entrants section is prioritised above creation UI for workflow efficiency. [oai_citation:2‡event_entrants.html](sediment://file_00000000f38c71f4967d8e95b84b0d20)

Entrants list

  • Displays all entrants
  • Search filter (name/email/race/faction)
  • Shows type (Registered / Guest)
  • Shows race + faction

Entrant types

Type Behaviour
Registered
  • Read-only
  • Can be deleted
Guest
  • Editable
  • Supports claim flow

Entrant actions

Action Description
ArmyNavigate to army management
EditEdit guest entrant
DeleteRemove entrant
Regenerate claim emailGuest only

Registered user flow

  1. Search user
  2. Select result
  3. Add to event
  4. List refreshes

Single-click addition workflow. [oai_citation:3‡event_entrants.js](sediment://file_00000000dfdc720a802df47c71980d8b)

Guest entrant flow

  1. Enter display name
  2. Optional email + notes
  3. Save
  4. Optional claim code generated

Claim system

  • Guest entrants can be claimed later
  • Claim email can be resent
  • Tracks claim code usage

Email-based auto-conversion

If a guest email matches a registered user: → automatically converts to registered entrant

This prevents duplication and ensures correct identity mapping. [oai_citation:4‡event_entrants.js](sediment://file_00000000dfdc720a802df47c71980d8b)

State model

{
  currentEvent,
  allEntrants,
  editingGuestId
}

Search behaviour

  • Client-side filtering
  • Search across multiple fields
  • Instant update on input

Navigation

  • Entrant → Army page
  • Maintains event context via query string
event_entrant_armies.html?event_id=X&entrant_id=Y

Risks / observations

  • Multiple responsibilities in one page
  • Heavy dependency on API consistency
  • No pagination (could scale issue)
  • Search is client-side only

Recommended improvements

  • Add pagination for large events
  • Debounce search input
  • Improve loading indicators
  • Add bulk actions (future)

Architecture classification

This is a Management Hub:
  • Controls multiple workflows
  • Routes to deeper features
  • Central TO entry point