Battle Arena guide
Frozen Lineups and Reservations
Distinguish local choices, private plans, commitments, accepted lineups and temporary reservations in normal battles and league fixtures.
Search the official guide by question or keyword.
On this page
Beginner summary
A frozen lineup is the accepted record of the five Uppies, their fighting order and the battle information used for a contest. A reservation is the game's temporary hold that prevents those Uppies being submitted into conflicting battles. Frozen history can remain after reservations are released.
Selecting cards, saving a future plan, accepting an invitation and submitting a lineup are different actions. Knowing which action you have completed prevents both accidental commitments and missed submissions.
Detailed explanation
The states players need to distinguish
| State | Meaning | Reservation and editing |
|---|---|---|
| Local selection | Cards chosen in your editor or picker | No competitive reservation; editable until submitted |
| Planned future lineup | Your intention for a later normal-series match | No advance reservation; editing depends on commitment rules |
| Accepted invitation | You have joined the contest | Does not submit your squad; the creator's first squad was already submitted |
| Committed plan / Locked in | An active-series choice you must honour | Still no reservation solely from the plan; ordinary editing closed |
| Accepted battle submission | The game confirmed a legal lineup for this match | Frozen inputs and battle reservations; no free replacement |
| Saved league round selection | Your last confirmed choice for the active round | Editable before cutoff; rechecked and frozen during deadline processing |
| Historical frozen lineup | The saved inputs of an earlier submission | Remains recorded even after its reservation ends |
“Accepted” is context-sensitive. An accepted invitation is a participation decision; an accepted lineup is a confirmed squad submission. Neither a selected card nor a saved future plan proves that a match is ready.
Normal challenges freeze the first squad when sent
- Choose and arrange five eligible Uppies in Create Battle.
- Apply the picker selection and review the main form. At this point no battle hold has been created.
- Send Challenge. On confirmed success, the creator's first lineup is fixed and its five members are reserved while the invitation waits.
- The invited player accepts, prepares a lineup and submits it. On acceptance of that submission, their lineup is fixed too.
- The ready match resolves from those frozen inputs. You cannot change the five or reorder them simply because combat has not yet been shown.
For a normal series, each later team battle has a new accepted lineup and reservation. Existing reservations release when the completed match is processed. A future plan creates no hold between matches, so members must still be available at their next submission. Read Planning Future Squads before relying on automatic preparation.
League selections freeze at their own cutoff
The current league round form saves a selection that remains editable before its displayed deadline. Saved means the server confirmed the selection; a card arrangement still marked Unsaved has not replaced it. Use Update round lineup to submit changes and verify the confirmation.
At cutoff, editing closes even if processing has not finished. The game rechecks the latest confirmed selection and freezes eligible inputs. A later collection change does not revise that saved battle record. A Best-of fixture uses the accepted five and order throughout its constituent battles, with reservation handoffs between them and no tactical editing window.
If there was no new round selection, the competition's prior-lineup fallback may be checked. It is conditional, not a promise that any five from your collection will be chosen for you. An explicitly selected but invalid squad is not silently replaced by another squad. Deadline outcomes distinguish invalidity from technical uncertainty.
Why an Uppie may be unavailable
Competitive acceptance requires five different owned Uppies whose current information can be verified. The lineup must satisfy the chosen ruleset and costs, and each member needs a usable battle profile. Sale listings, changing ownership, another battle reservation, a wrong level/type or missing verification can prevent acceptance.
An asset visible in My Uppies is not automatically available for every contest. Use the current eligibility explanation in the builder. For normal Open, five costs must total 21–26 inclusive; a normal Uppie costs its level and an IPU costs 12. Exact-level and IPU-only rules have their own fixed totals. Building a Squad remains the detailed authority.
When reservations end
Normal challenge reservations release through confirmed battle completion or the permitted cancellation, decline and expiry cleanup. In a series, an unused future plan never acquired an advance reservation to release. A league fixture's holds follow its fixture processing rather than a player's desire to edit between constituent battles.
Closing a browser, navigating away, refreshing or waiting until a displayed clock reaches zero does not itself release a hold. The relevant processing must complete. If a result or cleanup is delayed, inspect the existing contest and its latest status. Avoid creating another challenge to try to force an unlock.
Applicable rules and availability
These are the current local normal-series commitment and league-round selection policies. Their implementation is distinct from deployment and operational availability, which this guide has not verified. Background processing is involved in plan activation, league freezing and some cleanup.
The frozen record supports the battle that was actually accepted. It does not permanently freeze an Uppie's collection card, prevent every external ownership change or guarantee eligibility for future matches. Each context applies its own checks at the required boundary.
Important exceptions
A ready battle uses its accepted frozen inputs. League Best-of fixture activation also checks ownership/availability before beginning the fixture series; once begun, the accepted fixture squad/order remains fixed. Normal future matches receive fresh submissions rather than copies of an old injury state.
If a response is lost, confirmation is uncertain. Use the same retry offered by the form. A safe retry recovers the saved action instead of creating a second reservation. If the window closes during an unconfirmed league submission, refresh to inspect the last confirmed selection; local unsaved choices do not become valid retroactively.
Practical examples
Frozen does not mean still reserved forever
You finish Match 1 and see the original five in its historical lineup. Its holds have been released. The record remains so the battle can still be explained; seeing those five in history does not mean they are unavailable for all future play.
Two different uses of Locked
Your future Match 3 reads Locked in because the plan is committed. Match 2 reads Submitted / locked because its lineup has been accepted and reserved. Only the second state describes a current battle hold. You cannot freely edit either, but for different reasons.
A league update that was never saved
You submit A, B, C, D, E for a round. Later you rearrange the editor to E, D, C, B, A but do not confirm Update round lineup before cutoff. The first saved order remains the submission. An unsaved arrangement is not evidence that processing used the wrong order.
Strategic considerations
Track outstanding reservations before arranging another contest. Plans can simplify preparation, but they do not protect a favourite Uppie from conflicts elsewhere. Leave enough time for availability checks and confirmation rather than relying on a last-second click.
Review the exact stage before acting: editing a league selection, repairing a failed current series plan and submitting a fresh current lineup are different opportunities. Use only the action the contest currently offers.
Common questions
| Question | Answer |
|---|---|
| Does Apply squad lock my five? | No; it only applies the picker choices to the editor |
| Can I freely swap a frozen fighter before watching? | No; watching does not define the edit cutoff |
| Why is a card visible but unavailable? | Collection visibility and current competitive eligibility are different |
| Does a future plan prevent another reservation? | No; availability is checked again when that plan is submitted |
| Will selling an Uppie rewrite an old battle? | No; recorded historical inputs remain |
| Why are locks still shown after a deadline? | Cleanup may still be pending; check the contest's confirmed status |
| Does a new battle carry old combat injury? | No; temporary damage and fatigue reset for the new team battle |
Historical versions
Historical normal series can have cadence-based fallback and may lack planning. Earlier league submission flows could freeze directly rather than use today's editable round selection. Existing accepted historical lineups are not retroactively reopened. Use the recorded policy and state; do not apply the current editing window to an already frozen record.
Related topics
- Building a Squad
- Planning Future Squads
- Battle and Series Deadlines, Forfeits and No Contest
- Normal Battles vs League Fixtures
- Survivor Health and Workload Fatigue
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.