Battle Arena guide
Player and Uppie badges
Understand the five existing local badge definitions, their public requirements and the difference between recorded awards and the unfinished collection view.
Search the official guide by question or keyword.
On this page
Beginner summary
Understand the five existing local badge definitions, their public requirements and the difference between recorded awards and the unfinished collection view.
Detailed explanation
Existing badge definitions
A player badge belongs to the player account. An Uppie badge records that particular Uppie's accomplishment. These are the five badge definitions verified in the local implementation. Their deployment and live availability have not been verified by this documentation review.
| Badge | Recipient | Verified local requirement |
|---|---|---|
| First Steps | Player | Complete 1 qualifying Production-linked team battle |
| First Victory | Player | Win 1 qualifying Production-linked team battle |
| Battle Tested | Player | Complete 10 qualifying Production-linked team battles |
| Ten Victories | Player | Win 10 qualifying Production-linked team battles |
| Goliath | Uppie | A normal Level 1–10 Uppie defeats a Level 11 IPU in an actual qualifying individual fight |
What awarding checks
Awards follow verified recorded outcomes, not a browser claim or replay click. Match-count badges count eligible team battles across supported Classic and Winner Stays records; they do not count one event for every duel. Goliath uses the actual fighting members and their recorded battle levels, not an unused member or a later change to the current asset.
Award processing follows the authoritative battle result. A badge-processing failure does not invalidate that battle. Retrying processing is designed not to duplicate or overwrite an existing award. This does not guarantee that recovery is currently operating or that a particular missing award will arrive immediately.
Understand and check your progress
A qualifying team battle is a completed, eligible combat result attached to the verified players, not merely an invitation or a League fixture awarded without fighting. Each eligible team match in a series can count separately. A Best-of-3 result of 2–1 contains three team matches: it can contribute three participation counts and two wins for the winner, provided all three meet that badge’s eligibility rules.
- Identify the recipient in the table. Your player participation badges are not added to every Uppie in your squad. Goliath belongs to the fighter that actually defeated the IPU.
- Compare eligible team battles or wins with the requirement. At nine eligible team battles, one more reaches Battle Tested; a loss still counts. At nine eligible wins, another loss does not reach Ten Victories.
- Use Battle History and the saved results to check which matches really occurred. The visible player totals can have different viewing and historical limits from badge eligibility, so they are a guide to checking records, not a dedicated badge-progress counter.
- In an owned profile, Badges earned counts that Uppie’s currently displayed awards. It does not show “9 of 10” progress toward a player badge. View Badges still opens the Coming Soon collection message.
- If an expected award is absent, keep the relevant battle reference and distinguish an unavailable read from a successful read with no award. No currently verified progress bar, claim button or dedicated player-badge navigation is promised here.
Separate older Uppie detail pages can show a Badges / Achievements list with badge names, descriptions, difficulty and earned dates. That list is different from the current collection dossier’s count and Coming Soon dialog. Do not expect clicking View Badges in the dossier to open it.
Applicable rules and availability
Eligibility requires supported resolved standard/competitive combat with qualifying Production-linked participants. Practice, development/test records, unfought byes/forfeits and replaying do not manufacture match or fight awards. Definition activation/version eligibility also matters; not all old battles are automatically counted under a later definition.
These rules describe local implementation evidence. They do not establish deployment or live operation.
Important exceptions
The current dossier displays an earned badge count when loaded, but View Badges opens Badges — Coming Soon for collections. Public Scout does not provide the earned-badge reader. An empty successful read and an unavailable read are different. Goliath is an accomplishment badge, not the Giant Killer Ability.
Practical examples
Ten qualifying team battles can earn Battle Tested even if some were losses. Ten individual duels within fewer than ten team battles do not meet that requirement. A normal fighter beating an IPU can meet Goliath even when its team later loses; simply sharing a winning squad cannot.
Strategic considerations
Focus on the actual requirement and eligible combat rather than replaying or farming Practice. Badge difficulty labels are descriptions, not extra squad points or combat bonuses. No new badge, collection reward or combat benefit is promised here.
Common questions
| Question | Answer |
|---|---|
| Does watching again award another badge? | No. Repeated viewing does not create a new qualifying outcome. |
| Does Goliath require a team win? | The verified requirement is the normal Uppie's individual defeat of an IPU. |
| Is a Coming Soon dialog proof my earned badges vanished? | No. It describes the unavailable collection view. |
Troubleshooting
For Earned badge count unavailable, use Retry badges to retry the read. This button is not an award-processing control. If a known qualifying result appears to lack an award, retain the battle reference and report the visible state; do not assume the loading failure is fixed.
Historical versions
Normally, a battle must have resolved at or after the active badge version became available to count toward that version. This applies to the matches used to reach a count requirement as well as to a one-fight accomplishment. An older completed match does not become newly eligible merely because it is watched or checked later.
The original versions of the five badges above have a specific exception: eligible legacy delayed challenges can count even if they resolved before that version’s activation. That exception does not include every old competition. Later rule versions and reactivated definitions use their new activation boundary. The public screens described here do not expose an activation-date audit, so keep the relevant match references if this distinction needs checking.
An earned badge is recorded once for its player or Uppie. Repeated processing and later versions preserve the existing award rather than adding duplicate copies. These rules do not promise that all historical results have been processed or that a missing award will be recovered immediately.
Related topics
- Badge collections and tiers
- Achievements and Coming Soon features
- What counts as qualifying participation
- Player combat statistics
- Individual Uppie career statistics
- Uppie Levels and IPUs
Review metadata
Revision 2. Reviewed against local source and test evidence on 2026-10-17. Owner editorial and protected-information approval recorded on 2026-10-17 for the local Game Guide. Deployment and live operation remain unverified.