Battle Arena guide
Troubleshooting career and badge loading
Recognise loading, empty, partial and unavailable states and use the separate statistics and badge read retries.
Search the official guide by question or keyword.
On this page
Beginner summary
Recognise loading, empty, partial and unavailable states and use the separate statistics and badge read retries.
Detailed explanation
Read the message before retrying
| Visible state | Meaning and next step |
|---|---|
| Loading career statistics… / Loading earned badges… | The corresponding requested read has not completed |
| No visible recorded individual fights | A successful visible-career read found no fights in its authorised usable scope; not proof of no lifetime combat |
| Partial coverage | Only complete usable authorised records contribute; inspect the coverage explanation |
| Career statistics unavailable. Please retry. | The read could not supply usable data; use Retry career statistics |
| Earned badge count unavailable | Badge read failed; use Retry badges |
| Badges earned: 0 | Successful current badge projection contains no active earned entries |
| Badge collections — Coming Soon | The collection interface is intentionally unavailable; retries do not activate it |
Retry the affected reader
Open the intended owned Uppie in My Uppies, check its ID and use the specific retry shown in that profile. Career and badge reads are separate; one can fail while the other succeeds. Switching profiles must not be interpreted as a continued read of the old Uppie.
Public Scout intentionally does not expose owner career statistics or earned badges. Moving to Scout is not a workaround for protected career access.
Applicable rules and availability
Current ownership is necessary for the owned career reader but does not grant all previous-owner private battle history. Visibility and earlier-series reveal checks still apply. Partial or unavailable values must not be displayed or interpreted as confirmed zeros.
These rules describe local implementation evidence. They do not establish deployment or live operation.
Important exceptions
Real Career Statistics Loading Failure remains paused, unresolved and pending authenticated browser verification and manual acceptance. Local implementation and retry controls do not establish that the real failure has been repaired. Retry badges repeats a read; it does not trigger award processing.
Practical examples
You see a successful Discovery/Bond section, unavailable statistics and a badge count. This is possible because they are separate data paths. A Coming Soon badge dialog alongside a count is also expected and does not prove the count was lost.
Strategic considerations
Resolve the data scope before comparing performance. An unavailable reader cannot support a ranking or a claim that one fighter has never won.
Common questions
| Question | Answer |
|---|---|
| Is refreshing proof the bug is fixed? | No. The intended data must actually load and be verified. |
| Should I sell and rebuy the Uppie to fix access? | No. A transfer is not a loading repair and changes the Bond relationship. |
| Can I ask for another owner's hidden records? | Current ownership does not bypass historical privacy. |
Troubleshooting
If retries fail, retain the visible Uppie ID, status wording, time, whether other sections loaded and the steps taken. Report through an owner-confirmed support route. Do not paste session data, private logs or credentials. A general support-ticket destination has not been verified in this guide.
Historical versions
Legacy team aggregates and current individual records use different definitions. A historical count mismatch can be a scope difference rather than this loading failure; the approved legacy guide explains the distinction.
Related topics
- Individual Uppie career statistics
- Legacy records and partial coverage
- Player combat statistics
- Watching and replaying battles
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.