Skip to guide content

Battle Arena guide

Schedules, repeat meetings and idle rounds

Understand full-capacity and deadline starts, creator attention controls, round timing, one to three meetings, idle rounds and delayed processing.

Reviewed Revision 1
On this page

Beginner summary

A league has two different clocks. The registration deadline limits entry. Once play starts, each round gives players a selection window before its scheduled fixture-processing time. Saving a squad is not a request to fight immediately.

Watch the league's current state and displayed local deadline. A countdown reaching zero closes editing; it does not prove that background processing has finished. Missing results alone are not a loss.

This article explains starting, round timing, repeated meetings, idle rounds and schedule troubleshooting. To enter a league, see Creating and joining competitions. To handle fighter eligibility or missed selections, see Round squads and submission windows.

Detailed explanation

When registration becomes a running league

The creator is accepted automatically. Other players must join or accept an invitation. Invited players reserve places but do not count as accepted until they respond.

Table 9: Start condition, What happens in the current lifecycle
Start conditionWhat happens in the current lifecycle
Accepted players reach configured capacityRegistration starts the league automatically as part of the final acceptance/join processing
Deadline is reached with enough accepted playersBackground processing starts the league using accepted entrants
Creator chooses Start league with enough accepted playersThe league can start early without waiting for full capacity or the deadline
Deadline is reached with too few accepted playersProcessing marks registration as needing attention; the league does not invent players or automatically become a completed competition
Every place is reserved but some invitations remain unansweredReserved capacity alone does not start play; accepted count determines the start conditions

The minimum is two accepted players for Knockout or Round Robin without finals, four for Top 4 straight finals and eight for Top 8 straight finals. Capacity must also support the selected finals. These counts include the creator. A two-player Round Robin is supported; do not assume it needs three or four.

Successful start closes entry and creates the competition's bracket or meeting schedule from the accepted entrants. An unanswered invitation is not an entrant. Starting a league opens the first round's preparation window; it does not resolve a battle immediately.

Creator extensions and cancellation

While the league remains in Registration, its creator can use New registration deadline (local time) and Extend registration to set a valid future deadline. This clears the registration-attention flag and lets eligible players join or accept while the new window is open. Existing entrants and configuration are preserved.

Despite its label, this control validates that the replacement time is in the future, not that it is later than the previous deadline. Check both dates. Other fixed settings, including capacity and Rules, do not change. An extension cannot reopen entry after the league becomes Active, and cannot lengthen an already active round's squad deadline.

Cancel league is also a pre-start creator control. It cancels the competition and closes joining; it does not create battle results or a champion. It is not an in-play rescue option for a missed squad deadline. If starting and a creator action happen close together, the confirmed current state determines which action is still permitted. Refresh instead of assuming the earlier screen remains authoritative.

Follow the first round

  1. Open your league from My Leagues after creation or joining.
  2. Check that the league is Active, then find Current round and Scheduled start (local).
  3. Check Your fixture for your opponent, or the message explaining that no fixture is required.
  4. Prepare and confirm your squad before the displayed scheduled time. You can update a current saved selection while the window remains open.
  5. At the deadline, expect Scheduled time reached · awaiting processing, Lineups locked, or Processing, depending on the last confirmed state.
  6. Check the confirmed fixture outcome and the next active round's deadline. Do not assume all later round times are already fixed.

The league screen calls the deadline the scheduled start because that is when fixture processing becomes due. The round's preparation period begins earlier. For example, a round opened at 09:00 with a one-hour window has a 10:00 selection deadline and scheduled processing time.

How later rounds are scheduled

Rounds advance sequentially. A later round waits for the preceding round to complete; one player finishing their own fixture is not enough if other required fixtures remain unresolved. A Best-of fixture must finish its series before its parent fixture is complete.

Each newly scheduled round receives its configured selection window from its scheduled opening time. The existing scheduler also honours a recorded earliest cadence between round openings. The current creation screen supplies a one-second cadence internally and exposes Time per round as the player control; there is no separate cadence setting to adjust. Because a round must finish first, this does not create a new playable round every second.

Processing delays can move later openings and therefore later deadlines. For older or separately configured schedules, an already recorded start time remains relevant. Always use the active round's displayed deadline. A later processing pass is not a promise of extra selection time for a round whose deadline has already closed.

Round Robin meetings and idle rounds

Meetings per opponent is 1, 2 or 3. One meeting means one fixture against each other player. Two or three meetings repeat those pairings as separate fixtures; they do not mean two or three constituent battles within one fixture. Fixture length independently chooses Single Match, Best of 3 Matches or Best of 5 Matches.

For an even number of accepted entrants, one meeting cycle takes one fewer round than the number of entrants. For an odd number, one cycle takes as many rounds as entrants and each player has one idle round. Multiply by the selected meeting count. A player has at most one fixture in a round.

Table 26: Accepted entrants, Meetings each, Round Robin rounds, Fixtures per player, Idle rounds per player
Accepted entrantsMeetings eachRound Robin roundsFixtures per playerIdle rounds per player
23330
41330
42660
31321
33963

These counts exclude any finals. They use actual accepted entrants at start, not empty configured capacity. An idle Round Robin player has No fixture this round and needs no lineup for that round. It is not a forfeit, a free combat win or a new qualifying combat appearance.

Knockout byes and blocked progress

Knockout accepts 2–64 entrants, including non-power-of-two counts. The bracket can contain a Bye, which advances a player without a fight; no squad is needed for that bye. This is different from a Round Robin idle round, where nobody advances through a bracket.

A missing winner from an unresolved fixture or a double forfeit is not automatically converted into a bye. A Knockout round can need attention because no valid winner exists to advance. Do not assume that waiting longer creates a winner. Detailed bracket, standings and finals rules are outside this article.

Deadlines and background processing

Players can save and edit selections only before the round deadline. Both lineups submitted means both have saved choices; it does not advance the scheduled start. At or after the deadline, background work checks current eligibility, freezes accepted lineups and resolves ready fixtures. Technical problems can leave checks pending.

The current implementation contains background processing for registration expiry, round activation, eligibility checks and results. This guide has not verified that hosted workers are deployed or running. A deadline is a rule for when actions close or processing becomes due, not a guarantee of immediate result delivery. Keeping the page open, watching its countdown or pressing refresh is not a substitute for successful background processing.

Applicable rules and availability

This describes the current locally implemented league-registration and round-selection lifecycle. The setup form creates scheduled delayed leagues. Source and selected local checks support these rules; they do not establish production availability, manual acceptance of every interface or continuous worker operation.

Times are displayed in the viewer's local time zone. Players in different locations can see different clock times for the same deadline. Coordinate using the date and time zone, especially across daylight-saving changes. There is no universal daily start hour and no automatic 24-hour registration window: the creator selects the deadline and the round duration.

Important exceptions

  • Filling accepted capacity can start registration early, before the chosen deadline. Filling capacity with invitations alone cannot.
  • Too few accepted players at expiry means Needs attention, not automatic cancellation or fabricated matches. The creator may extend or cancel before start.
  • Registration controls cannot repair an active round's missed cutoff.
  • A pending technical check is not proof that a player failed. Forfeit policy depends on confirmed selection/eligibility state, explained in Missing or invalid selections.
  • An idle round or bye creates no combat progression by itself.
  • Round Robin results can complete without a fixture winner after a double forfeit; a Knockout bracket may remain blocked when it needs that winner. This article does not define ranking consequences.

Practical examples

Starting before the advertised date

An eight-place league is scheduled to close registration tomorrow. Its eighth accepted player joins today. The league starts automatically and opens its first round. The configured round duration now matters; players should check the actual active deadline rather than waiting until tomorrow.

Registration expires with too few finalists

A Top 4 league has three accepted players when registration closes. Three cannot supply four finalists, so deadline processing marks it as needing attention. The creator can choose a future deadline or cancel while it remains in Registration. The creator cannot turn it into a No finals league by editing the original setting.

Everyone submits early

A round's scheduled time is 18:00. Both players save valid-looking squads at 12:00. They can still update before 18:00, and the fixture waits. At 18:00 editing closes; fresh eligibility checks and processing may finish later. A result appearing at 18:03 does not mean the submission deadline was extended to 18:03.

A delayed previous round

Round 1 has a one-hour selection window, but one fixture needs extra verification after cutoff. Round 2 waits for Round 1 to complete. Once Round 2 opens, check its own displayed one-hour window. Do not calculate its cutoff solely from the original competition start time.

Repeated meetings with a longer fixture

Four accepted players choose two meetings per opponent and Best of 3 Matches. There are six Round Robin rounds and each player has six fixtures. Each fixture ends when someone wins two battles, so a meeting can take two or three battles. The meeting count is not the number of battles required to win a fixture.

Strategic considerations

Agree enough preparation time for everyone before creating the league. Check again when a league fills; automatic start can bring the first cutoff forward. More meetings create more separate preparation windows. In an odd-player Round Robin, use idle time to check fighter availability for your next real fixture. Avoid relying on predicted dates for later rounds when earlier fixtures remain unresolved.

Common questions

Table 53: What I see, What it means and what to do
What I seeWhat it means and what to do
Registration with every place reservedCheck accepted count; pending invitations do not start the league
Registration needs attentionCreator should review the required accepted count and use available extension/cancellation controls
Deadline passed, still RegistrationEntry has closed; expiry processing may not yet have completed. Refresh confirmed state
Both lineups submittedSaved choices are waiting for the scheduled time; no early fixture trigger
Scheduled time reached · awaiting processingEditing is closed; a result is not yet confirmed
Lineup revalidation pendingEligibility cannot yet be established; it is not itself a forfeited result
Between rounds · the next round is awaiting activationThe next active round is not confirmed yet
No fixture this roundAn idle round requires no squad; check the next round when available
Updates unavailableThe page may show last-confirmed information; use Retry league before relying on action controls

When to report a scheduling problem

Refresh the league and check its last confirmed status, current round, deadline, accepted count and any attention message. If it is your league and still in Registration, use the available creator controls for a participation problem. If the schedule remains stuck or eligibility verification repeatedly fails, record the league-page address, round, displayed deadline, your time zone and the visible status/error for an available official contact channel.

No fixed processing-time guarantee or working in-app ticket system is established here. Do not declare a win or loss from a delayed screen alone, and do not create another competition merely to retry an uncertain request. Repeated refreshes cannot manufacture a missing authoritative result.

Advanced rules

Round counts describe the competition structure, not a guaranteed calendar finish. The accepted entrants, meeting count and any finals determine which contests are required. Their actual completion, verification delays and recorded scheduling settings determine when later rounds can open. A still-unresolved opponent is not interchangeable with an empty bracket seat.

Repeating a confirmed start or membership action does not generate a second schedule. Recheck the existing league when confirmation is delayed rather than creating a duplicate competition.

Historical versions

Older league schedules were created with one meeting per opponent; the later 1/2/3-meeting option does not rebuild those schedules. Older configurations may have a different cadence or supported execution mode. Earlier direct frozen submissions also differ from today's editable round selections. Use the recorded league state and controls, rather than applying every new-creation feature to an old competition.

The automatic registration lifecycle described here is distinct from historical creator-start flows. Historical rules and completed results remain intact. Current or historical ranking versions do not turn a delayed processing result into proof of a loss; detailed ranking and finals explanations are reserved for later guides.

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.

Back to top ↑