Battle Arena guide
Reporting a gameplay problem
Prepare a concise, privacy-safe problem report with the visible context needed to distinguish a rule from a failure.
Search the official guide by question or keyword.
On this page
Beginner summary
Prepare a concise, privacy-safe problem report with the visible context needed to distinguish a rule from a failure.
Detailed explanation
Prepare the report
A useful report describes what you tried, what happened and what you expected under the official rule. It is not a request to share account credentials or another player's private history.
- Note the visible contest reference or Uppie ID relevant to the issue. Use only identifiers you can legitimately see.
- Name the page and action, such as Create Battle → Send Challenge, Battle History → View / Replay, or My Uppies → Retry career statistics.
- State the style, series/fixture context and ruleset if relevant.
- Record the time and timezone, displayed deadline, status and exact visible error.
- List short reproduction steps and whether the offered retry changed anything.
- Compare the result with the related official rule. Say if you are unsure which count or version applies.
- Share through a support route confirmed by the project owner. No dedicated support-ticket form, address or automatic submission mechanism is established by this documentation.
For screenshots, crop to the relevant message and remove connection codes, private account information and unrelated player data. Do not attach full diagnostic dumps or browser storage.
Applicable rules and availability
Submitting a report does not extend a deadline, cancel a contest, change its result or guarantee a backfill. A local implementation check is not deployed or operational verification. Preserve the existing attempt when submission success is uncertain.
These rules describe local implementation evidence. They do not establish deployment or live operation.
Important exceptions
The known real career-loading failure remains paused and unresolved, pending authenticated verification. Report observed symptoms without stating that it is repaired. Coming Soon collections and deliberate Scout privacy exclusions are unavailable features/access boundaries, not automatic bugs.
Practical examples
A useful fictional report: “At 14:20 Australia/Sydney, I opened profile ID 123 in My Uppies and selected Retry career statistics once. The message remains ‘Career statistics unavailable. Please retry.’ Discovery and badges load. I expected a successful visible-career read, not hidden former-owner records.” Include the actual visible wording in a real report.
Strategic considerations
Keep the report focused on one reproducible issue. Distinguish a missing read from a missing award and a team win from an individual win; this helps identify the affected system.
Common questions
| Question | Answer |
|---|---|
| Should I send passwords or connection codes? | No. Never include them. |
| Must I create another battle to demonstrate a lost response? | No. Preserve the existing attempt and check its status first. |
| Will reporting reverse a forfeit? | No such outcome is promised. |
Troubleshooting
Before reporting, clear irrelevant collection filters, verify the intended account, read the current contest state and use only its existing offered retry. Stop repeated actions if the result is uncertain. If no confirmed support route is available, retain the report for the owner instead of sending it to an invented destination.
Historical versions
Include a visible historical version when available. Current rules should not be used to assert that a correctly recorded older battle was invalid.
Related topics
- Legacy records and partial coverage
- Battle and Series Deadlines, Forfeits and No Contest
- Battle history and result states
- Individual Uppie career statistics
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.