Battle Arena guide
Normal Battles vs League Fixtures
Compare normal challenges with scheduled league fixtures: entry, squad editing, frozen Best-of lineups, timing, results and progression.
Search the official guide by question or keyword.
On this page
Beginner summary
A normal battle begins with a player-created challenge to a named opponent. A league fixture is a scheduled contest inside a larger competition. The combat style can be the same, but opponent selection, lineup editing, deadlines and the meaning of the result differ.
This is an introduction to leagues and tournaments, focused on those differences. Detailed registration, schedules, standings, finals and bracket rules are separate planned guide topics. This article does not replace those future references.
Detailed explanation
A small competition glossary
- Fixture: one scheduled meeting between two players. It can contain one team battle or a Best-of series.
- Round: a scheduled group of fixtures with its own submission window. An idle player has no fixture to submit for in that round.
- Round robin: a competition where scheduled meetings between entrants contribute to standings.
- Standings: the competition table that ranks entrants using its recorded results and tiebreak rules.
- Knockout: a bracket where fixture outcomes determine advancement; it is distinct from a league standings table.
- Finals: a later competition stage when the selected league format includes one. Not every league has finals.
Compare before entering
| Choice or event | Normal challenge | Current league fixture |
|---|---|---|
| Opponent | Creator names and verifies another connected player | Competition schedule or bracket assigns the opponent |
| Entry | Invited player accepts the challenge | Join/register through the competition's supported public or private flow |
| Battle style and ruleset | Creator chooses the offered settings before sending | Selected for the competition; each fixture follows them |
| Length | Single Match, Best of 3 Matches or Best of 5 Matches | Single or supported Best-of fixture length configured for the competition |
| First squad | Creator submits with Send Challenge; invitee submits after accepting | Save the active round's selection before its cutoff |
| Editing | Accepted match lineup is frozen; chosen active-series plans are commitments | Current round selection remains editable before cutoff, then freezes |
| Later battles in a series | Fresh lineup required per battle; chosen plans may prepare it | Same accepted five and order throughout the fixture |
| Timing | Normal invitation and Single/series clocks | Competition registration, round schedule and submission cutoff |
| Overall result | One normal contest result and its recorded battles | Fixture result contributes to standings or bracket advancement |
Join and find the scheduled contest
- Open Leagues in Battle Arena navigation and inspect the competition you intend to enter. Check its rules, registration status, fixture length and schedule.
- Use its supported registration route. Public registration and private invitations/join codes have different entry requirements; being able to see a competition does not guarantee entry is open or a seat remains.
- Confirm your accepted entry. Registration alone is not a submitted round squad.
- Once the competition is active, check the scheduled opponent and current round. Do not create a separate normal challenge to fulfil a league fixture.
- In Your round lineup, choose five eligible Uppies in fighting order, then use Submit round lineup. Confirm the Saved state.
- If you change members or order while the window is open, use Update round lineup and confirm again. Unsaved changes do not replace the last confirmed selection.
- At the displayed deadline, editing closes. The game checks current eligibility, freezes the accepted lineup and processes the fixture.
Registration and scheduling are separate from combat. The current lifecycle can start a competition when its seats fill or process it at registration close if it has enough accepted entrants. Insufficient entrants require organiser attention; the clock alone is not proof that a schedule or winner exists. Round timing is configured for the competition, so read the displayed deadline rather than assuming normal battle timings apply.
One fixture can contain several battles
A Single fixture needs one team-battle win. A Best-of-3 fixture needs two; Best-of-5 needs three. It stops when someone clinches the fixture. The winner contributes one fixture outcome to the parent competition, even if several team battles were fought.
The accepted fixture squad and its order stay fixed for every constituent battle. The game prepares those battles from the fixture's frozen inputs, with fresh temporary combat state. It does not invite a tactical squad change after each result, and it does not carry prior combat damage into the next team battle.
For example, a Best-of-3 fixture that ends 2–1 has three recorded team battles and one fixture winner. The 2–1 fixture-series score is different from a Classic battle score of 3–2 and from the player's total wins in league standings.
Why two saved squads may still be waiting
Saving both round selections early does not make the fixture resolve immediately. Players retain the configured editing window. At cutoff, the latest confirmed selections must pass eligibility checks and be frozen; background processing then resolves the scheduled contest.
An elapsed cutoff also does not prove that processing finished. A temporary verification failure may keep the fixture pending. The UI can be read-only while the result is still being processed. Refresh the league to inspect the confirmed state rather than assuming an empty result means a player forfeited.
Applicable rules and availability
The comparison describes current local normal challenges and the current delayed league-round selection flow. Normal invitations last 24 hours; normal Single Match lineups get 60 minutes after acceptance; new normal Best-of series get 24 hours after acceptance for the whole series. None of these is a universal league-round deadline.
Every squad has five different eligible Uppies and must meet the competition's rules. Read the actual minimum/cap and exact-level or IPU restriction. The local configuration supports Single, Best-of-3 and Best-of-5 fixtures, but not every combination of fixture length, timing mode and finals format is allowed. In particular, Best-of fixtures require delayed mode, and Top 8 double-chance finals do not support a Best-of fixture length greater than one. Do not infer additional options from generic engine capabilities.
These rules are locally implemented and supported by inspected source/test evidence. This guide does not establish deployed availability or that registration, freezing and resolution workers are operational.
Important exceptions
Where a league permits prior-lineup fallback, missing a new round selection can cause the earlier lineup to be checked again. A valid prior lineup may be carried forward; genuine ineligibility can lead to a forfeit. This is neither automatic selection of a new team nor the current normal-series deadline policy.
A forfeit or bye can affect competition advancement without a fought battle. A bye is advancement without a paired opponent in that position. It is not proof that any Uppie participated. Actual constituent combat supplies qualifying progression under the normal participation rules; the parent fixture's administrative result does not add another imaginary fight.
Detailed standings calculations, repeated meetings, idle rounds and finals paths remain outside this overview. Ordinary battle records and league standings measure different things and should not be expected to show identical totals. Historical records and player-specific reveal/visibility rules can also affect what is shown.
Practical examples
Same style, different preparation
You arrange a normal Winner Stays Best of 3 and leave Match 2 as Decide later. You may choose a different legal squad for that match before the shared deadline. In a league Winner Stays Best-of-3 fixture, your accepted lineup/order is fixed for the whole fixture; losing its first battle does not open the squad editor.
Both players submit early
Your league round has a displayed 20:00 cutoff. Both players save selections at 18:00. The fixture continues waiting through the editing window. You update your order and confirm it at 19:00. Processing at cutoff uses the last confirmed selection that passes eligibility, not necessarily your first saved order.
Fixture win versus battle wins
You win the first two battles of a Best-of-3 fixture. It ends 2–0; the third battle is unnecessary. The parent competition records one fixture winner. The two real battles retain their own results and eligible participation; no third battle is created to fill the schedule.
Strategic considerations
For normal series, decide which later slots deserve commitment and which need flexibility. For league fixtures, prepare a squad and order you are willing to use throughout the fixture. Check availability again before the round closes, particularly when the same Uppies are involved in other contests.
Choose the contest you actually mean to enter. Winning a separately arranged challenge against your scheduled opponent does not satisfy the league fixture or update its standings.
Common questions
| Question | Answer |
|---|---|
| Can I choose my league opponent each round? | The schedule or bracket determines the fixture opponent |
| Does accepting registration submit a squad? | No; check the active round's lineup requirement |
| Can I change my league selection before cutoff? | Yes while the current selection window remains open; confirm the update |
| Why is the fixture waiting after both selected? | Saved round choices wait for the scheduled cutoff and processing |
| Can I change squads between battles of one fixture? | No; accepted members and order remain fixed |
| Does a fixture forfeit earn combat participation? | No unfought result creates Discovery/Bond combat participation |
| Does a normal challenge count in league standings? | It is a separate contest, not the scheduled league fixture |
Historical versions
Earlier league flows could freeze submitted lineups directly rather than keep an editable round selection. Earlier fixtures may be single battles, and historical standings can use an older ranking policy. Preserve the meaning of the recorded contest; current features do not rewrite those results.
Historical normal series also used cadence and fallback rules distinct from current continuous timing. Historical deadline policies explain that boundary. This overview does not apply a new ranking formula to old standings.
Related topics
- Battles, Matches and Game Modes
- Single Matches and Best-of Series
- Frozen Lineups and Reservations
- Battle and Series Deadlines, Forfeits and No Contest
- Discovery, Bond and Combat Progression
- Planned detailed articles: Creating and joining competitions; Round squads and submission windows; Schedules, repeat meetings and idle rounds; Fixture series and scoring; Standings and tiebreaks; Knockout brackets and byes; Finals and qualification. These unwritten topics are listed as reading directions, not unavailable article links.
Review metadata
Revision 1, approved by the project owner on 2026-10-16 (Australia/Sydney) for the local Game Guide. Deployed and operational availability have not been verified.