Page body
What this surface does
This surface is the full create and edit screen for one tournament configuration.
The same route handles:
createmode, opened from the scheduler listeditmode, opened for one existing configuration row
How to use it
- Maintain the multilingual content block first so the public-facing tournament card has a usable name and copy.
- Set the schedule and recurrence carefully. The configuration controls how future instances are generated.
- Use
Lead TimeandLeg Timewhen the competition window should differ from the visible start/end timestamps. - Use player tags, provider/category/game filters, and opt-in flags to limit which players and gameplay are eligible.
- Maintain prize tiers separately so rank ranges and reward types are explicit.
- Use the translate action only after saving the current content, because the FE flow saves first and then calls the core translation endpoint.
Common caveats
- This surface edits the configuration row, not one already-generated active instance.
- Translation support for one record comes from the core tournament translation endpoint, not from
gs-admin-backend. - Assets, categories, and languages are loaded from core hooks even though the main create/update write path is the admin tournament controller.
- Prize tiers are saved inside the tournament configuration payload. There is no separate prize table in the operator UI.