Direct answer

Check the league panel in your current server and record the exact name, requirement, cost, lock reason, and update title. The developer confirms stronger leagues but does not publish a complete public requirements table.

Turn a locked prompt into an actionable checklist

These are categories for reading a prompt, not a confirmed list of Coach a Fighter gates. Copy the requirement exactly, mark met / unmet / unclear, and handle the first unmet prerequisite. If every visible condition appears met, record the prompt and your current state before a single fresh-server retry. A missing requirement must stay unknown; entering zero would imply that no requirement exists.

Requirement types to distinguish if displayed
Prompt refers toCompare againstDo not substitute
A cash amountCurrent available balance and the exact currencyA reward that has not yet been credited.
A gym or roster conditionThe current screen showing that conditionA similarly named upgrade or a rarity label.
A completed match or objectiveIts completion or result stateA previous attempt that did not complete.
Several conditionsEach condition individuallyOne satisfied condition for the entire gate.

Fields a trustworthy table needs

  • League name exactly as displayed.
  • Qualification requirement and lock message.
  • Entry cost or other required resource.
  • Roster, training, and gym context.
  • Promotion result, reward, date, and update title.

Read the live gate first

A search result can explain how to document the requirement, but the live interface remains authoritative for a changing beta value. Do not spend toward a number unless the current server displays it.

  • Capture the full requirement panel.
  • Avoid cropped images that hide the league name.
  • Record whether the gate is locked or merely unaffordable.

Protect the qualification cost

Keep the displayed entry or preparation cost outside the training and betting budgets. This prevents an optional experiment from delaying the next documented progression attempt.

  • Enter the cost as a protected reserve.
  • Recheck it after an update or server restart.
  • Record the remaining balance after the attempt.

Capture failed attempts too

A failed promotion or locked panel can reveal missing context that a successful screenshot does not show. Save the exact message and the roster or gym state used at the time.

  • Do not infer a hidden requirement from one failure.
  • Change one preparation variable before retesting.
  • Keep qualification and match result as separate fields.

Resolve conflicting requirement reports

  • Compare update titles and capture dates.
  • Check whether the reports show different leagues or lock states.
  • Keep both records until the context explains the difference.
  • Prefer the current live interface over an undated table.
Supported background
  • Stronger leagues are part of the official progression description.
  • The developer warns that balancing may change.
Details still to check
  • The full ladder and current requirements need live evidence.
  • League gates may include context not exposed in the public game description.

Sources and scope

Official links support the systems and labels described below. Decision tables, checklists and labeled worked examples are this site’s practical guidance, not measured game rules. Publisher and community material retains its own source status.