Battle Arena guide
Battle and Series Deadlines, Forfeits and No Contest
Check exact normal timing, ready matches after cutoff, distinct Single/series/league outcomes and preservation of legitimate combat records.
Search the official guide by question or keyword.
On this page
Beginner summary
A deadline is the cutoff for a required action. It is not a guarantee that the result will appear at that exact instant. Your confirmed submission state matters: choosing five cards or saving a future plan is not the same as having an accepted lineup.
A forfeit awards a contest outcome without normal combat deciding it. No Contest means no overall winner is recorded. Declined, cancelled and expired invitations also end without a fought result, but they are different lifecycle events. The outcome depends on whether you are playing a Single Match, a current normal series, a historical series or a league fixture.
Detailed explanation
The current deadlines
| Context | Time allowed | When it starts | What must happen |
|---|---|---|---|
| Normal invitation, any offered length | 24 hours | Challenge creation | Invited player accepts before expiry |
| Normal Single Match lineup window | 60 minutes | Invitation acceptance | The missing lineup must be accepted before cutoff; the creator already submitted when sending |
| Current normal Best of 3 or Best of 5 series | 24 hours for the entire series | Invitation acceptance | Complete the needed battles, with each required pair submitted before the shared cutoff |
| League round | The competition's configured window, shown for that round | The round's scheduled opening | Save the intended round selection before its displayed cutoff; eligibility is checked at freezing |
The normal invitation clock and the post-acceptance clock are separate. Accepting does not consume only the invitation's remaining time. It starts the applicable Single Match or series window. Conversely, a later match in a current series does not start a fresh 24-hour period.
Submit before, not at, the cutoff. A request started before the deadline can still arrive too late. Confirmed acceptance is the relevant event; a browser click or local card arrangement alone is not enough. No grace period or player-controlled extension is provided for current normal series.
Current normal outcome table
| Situation when processed | Outcome | Combat and progression |
|---|---|---|
| Invitee declines while the invitation is open | Challenge ends as declined/abandoned | No fought battle; reserved opening lineup released |
| Creator cancels before acceptance | Challenge cancelled | No fought battle; reservation released |
| No acceptance within 24 hours | Invitation expired/abandoned | No fought battle; cleanup releases reservations |
| Accepted Single Match reaches lineup cutoff while one side is still missing | Match abandoned, with no winner | No fabricated combat or forfeit win; submitted holds released |
| Single Match already has both accepted lineups before cutoff | Ready match remains resolvable afterward | Actual combat result and ordinary qualifying participation rules apply |
| Current normal series reaches cutoff with only one accepted lineup for the current unresolved match | That submitter wins the series by forfeit | No constituent combat result is invented; previous fought score stays intact |
| Current normal series reaches cutoff with neither current lineup accepted | Incomplete / No Contest | No series winner; previously completed battles remain recorded |
| Current normal series has both lineups accepted before cutoff | Resolve that ready match first, even after cutoff | If it clinches the series, complete normally; otherwise finish Incomplete / No Contest without starting another match |
| Series was already clinched | Existing completed result remains | Unneeded later plans create no fights or progression |
The Single Match missing-lineup outcome is deliberately different from the current series sole-submitter outcome. Do not call every missed deadline a forfeit.
Read the score and the outcome together
In a current normal Best-of series, the displayed fought score counts completed team battles. A terminal series forfeit does not invent extra matches to bring a player to two or three wins. A player behind 0–1 can still win the series by forfeit if they alone submitted for the next required match before cutoff.
A No Contest outcome similarly does not erase a legitimate completed battle. It says the overall series ended without a winner. Recorded earlier combat and its legitimate progression remain; it does not turn an unfought slot into a duel or award participation for unused plans.
League round outcomes
League rounds use their own schedule and lineup policy. A saved round selection stays editable until cutoff. At freezing, the game verifies the latest confirmed selection. If no new selection was saved, the supported prior-lineup fallback is checked against current eligibility; the game does not choose arbitrary replacements.
| League situation | Processing consequence |
|---|---|
| Both sides' selected or permitted carried-forward squads pass | Freeze the lineups and resolve the scheduled fixture |
| No new selection, but an eligible previous lineup exists | Freshly validate and carry it forward where the competition permits |
| No usable previous lineup and no selection | That side forfeits; with one valid opponent, the opponent wins the fixture |
| Explicit selection is genuinely ineligible at cutoff | That side forfeits rather than silently switching to another squad |
| Both sides forfeit | Double forfeit, with no fixture winner; broader advancement follows the competition's own rules |
| Eligibility verification is technically uncertain | Processing remains pending/retryable; uncertainty alone is not a confirmed forfeit |
A league forfeit can affect standings or advancement without producing combat scores, fight records or Discovery/Bond participation. A Best-of fixture checks eligibility when activating and then retains its frozen lineup/order throughout. It does not inherit the normal series' 24-hour completion policy or its mid-series squad choices.
Why a passed deadline may still show waiting
The countdown shows time; processing records the outcome. Background workers handle preparation, deadline checks, resolution and cleanup. Reading a page or refreshing its status does not itself guarantee that those operations have run. This guide verifies local implementation, not that workers are currently operational.
A temporary verification outage is not evidence that you sold an Uppie or selected an illegal squad. A ready-match resolution failure also leaves the existing ready pair retryable rather than replacing it with a fabricated result. However, uncertainty does not extend a normal series deadline. If a future plan never became an accepted lineup before cutoff, the current series' submitted-lineup rules still decide its terminal outcome. Do not interpret “retryable” as a guarantee that an unsent lineup will be accepted late.
Applicable rules and availability
Normal timing values above come from current local admission and lifecycle rules. League windows come from the actual competition configuration and displayed round, not a universal one-hour or one-day rule. Current normal creation does not offer a custom deadline control.
Background processing, deployment state and operational availability are separate from local code verification. No operational worker claim is made here.
Important exceptions
Cancellation closes after normal invitation acceptance. Do not confuse a pre-acceptance Cancel challenge with a way to avoid a later series loss. Expiry is not an instruction to submit after the clock reaches zero.
Current continuous series do not automatically revive the previous squad at cutoff. Explicit plans must activate and be accepted in time. Historical series and league fallback must not be copied into this policy.
Historical combat remains recorded, but a statistics screen can still have reveal requirements, coverage limitations or a loading problem. Preservation of a battle is not proof that every aggregate screen has loaded. See Discovery, Bond and Combat Progression.
Practical examples
Two clocks, one acceptance
You send at 09:00 Monday. The opponent must accept before 09:00 Tuesday. They accept at 18:00 Monday. For Single Match, the missing lineup is due before 19:00 Monday. For a current Best-of series, the shared completion cutoff is 18:00 Tuesday. Match 2 uses that same Tuesday cutoff.
A ready battle after cutoff
You lead a Best of 3 by 1–0. Both Match 2 lineups were accepted before cutoff, but processing finishes afterward. If you win, the series completes 2–0. If the opponent wins, the score is 1–1 and the series ends Incomplete / No Contest: a new Match 3 cannot start after the cutoff.
A lead is not enough
You lead a Best of 5 by 2–1. For Match 4, only your opponent's lineup is accepted before cutoff. The opponent receives the series-forfeit outcome. The fought score remains 2–1; it is not rewritten into three fabricated opponent wins.
A saved plan is not a submission
Both players have later squads planned, but the current needed match has neither lineup accepted at cutoff. The series closes without an overall winner. The existence of future plans alone does not make that match ready.
Strategic considerations
Accept only when you can act within the next window. Monitor Submitted / locked, Needs attention and the remaining time, not just a saved plan. Finish preparation early enough to recover from ordinary verification or confirmation delays.
In leagues, confirm your selection before cutoff even if you expect a previous lineup to remain eligible. Fallback is conditional. A new explicit choice that becomes invalid does not entitle you to a substitute after editing closes.
Common questions
| Question | Answer or next step |
|---|---|
| The countdown is zero; why is the result still waiting? | Processing may be pending; refresh the existing contest and inspect its confirmed state |
| Can I submit a new lineup after the cutoff? | No; a ready pair resolving afterward is a different case |
| Do I win a normal Single Match because only I submitted? | No; its missing-lineup policy abandons the match without a winner |
| Does a series forfeit add fictitious match wins? | No; read the overall forfeit outcome alongside the unchanged fought score |
| Does No Contest remove my earlier real battles? | No; legitimate completed records remain |
| What should I press when overdue? | Use Check battle deadline or Check series outcome when offered; for a ready match, Resolve match may be available |
| A request is unconfirmed; should I create another contest? | Check the existing status and use its safe retry; avoid duplicate challenges |
| What should I retain if a delay persists? | Keep the contest identifier, displayed state/time and visible error for review; do not share credentials |
Historical versions
Current continuous normal series use one 24-hour completion deadline, immediate next-match opening and no automatic cutoff fallback. Their terminal forfeit is a series result, not a fabricated constituent battle.
Historical cadence normal series used a 60-minute lineup window for each match and an hourly start cadence. Later starts cannot precede the previous scheduled start plus that cadence, but processing that finishes late need not add a further hour. At a missed later deadline, a previously submitted lineup can be freshly checked and carried forward. Genuine ineligibility or no available prior lineup can produce a constituent forfeit; unresolved technical verification remains pending. Two forfeiting sides abandon the series without inventing a winner. Those constituent administrative results are different from today's terminal series-forfeit policy.
Existing historical rows and their rules were not converted into new continuous series. Older/custom competition timings may differ again. Inspect the recorded contest rather than imposing the current normal defaults.
Related topics
- Creating and Sending a Battle Challenge
- Single Matches and Best-of Series
- Planning Future Squads
- Frozen Lineups and Reservations
- Normal Battles vs League Fixtures
- Discovery, Bond and Combat Progression
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.