POKÉMON CHAMPIONS
Beta Notes & Known Issues
What testers should expect today, the available workarounds, and where to report anything that feels wrong.
The core tools are ready for careful real-world testing.
Calculators, team building, account saves, public sharing, and the Windows edition are available. These notes call out the places where a tester may still need a workaround or a little extra review.
Links and screenshots may need review
- Private or deleted PokéBase teams cannot be fetched. Make the source team public, or import its text, JSON, or screenshots instead.
- Photo import is tuned for the two supported summary-screen layouts. Cropping, compression, glare, localization, or a different layout can reduce recognition quality. Review all six Pokémon, items, moves, and Stat Points before saving.
- Imported content still follows Regulation M-C. A structurally valid paste can be rejected when it contains an unavailable Pokémon, move, item, or form.
Online and device-only work have different homes
- Account teams, Pokémon, and calculator scenarios sync through the signed-in account. Match history, drafts, restore points, and several tool workspaces remain in that browser and should be included in a Library backup.
- Signing out does not erase the browser's account-scoped cache. Use account deletion and the Data Safety controls when you intend to remove data, especially on a shared computer.
- Apple sign-in is not part of this beta. Email and password, username, Google, and Discord are the supported online sign-in choices.
The portable app does not automatically sync with the website
The downloadable Windows edition stores its work on that computer and includes its own beginner launcher and backup tools. A web account and the portable app do not automatically copy libraries between one another. Keep the generated ZIP and use Library Backup before moving to another machine.
Start with a current browser during beta
Current Chrome and Edge on desktop receive the most frequent testing. Firefox, Safari, mobile layouts, keyboard-only use, screen-reader labels, blocked storage, slow networks, and multi-tab conflicts remain part of the active beta test matrix. If one browser behaves differently, include its name, device, and the exact page in the report.
Do not include passwords, sign-in codes, recovery codes, private team notes, or provider secrets in a bug report.
Send a small, reproducible report
- Open Help & App Info and copy the diagnostic report.
- Describe what you clicked, what you expected, and what appeared instead.
- Include a screenshot only after checking that it does not show private information.
- Use Report a bug to prepare the email and review it before sending.
For a calculation concern, include the visible Pokémon, move, item, ability, field settings, and displayed result. The diagnostic report intentionally excludes those battle details.