Early Access build · Version-aware player guide Open official build ↗

HELP & TROUBLESHOOTING

When something goes wrong

Find clear answers for controllers, crashes, compatibility, and common player questions.

02FAQ pagesChoose a topic

QUICK ANSWERS

Common questions from the research

Is there a native Android build?+

Not confirmed. The official listing targets Windows 10/11 64-bit, and the research notes say mobile is not planned.

Why is the first launch slow?+

The official page says shaders may take several minutes to compile. This can be normal on first launch.

What should I include in a crash report?+

Describe what you were doing and include the game's Saved/Logs/ file when contacting the official Discord.

Does the game support double battles?+

The current Early Access listing says single battles only; double battles were not completed for this build.

Is the old island demo the same game?+

No. The old demo is a separate historical, unsupported build. Keep it separate from the current Littleroot-to-Mauville Early Access.

Can I use a controller?+

Controller support is listed, but the official page recommends committing to one peripheral because switching can cause UI bugs.

KNOWN PLAYER REPORTS

Track issues without overstating them

These are recurring reports in the collected community material, not guaranteed bugs. They should be reported with the game version and logs.

AreaReported behaviorEditorial status
Controller inputSome players report PlayStation, Switch, or third-party controller detection problemsAnecdotal; test by device and version
Battle UISome reports mention battle buttons or inputs disappearingAnecdotal; report with logs
Loading / hitchingLow RAM, storage, or lower-end systems may pause during loads or battle eventsOfficial caveat plus player reports
World clippingPlayers have reported falling through gym or map geometryAnecdotal; do not treat as universal
Save updatesPlayers ask about save transfer after replacing an installBackup first; universal save path remains unconfirmed

SUPPORT FLOW

When something breaks

01Save often

Keep a recent save before testing updates or unstable areas.

02Record the action

Note what you were doing, the version, device, and input method.

03Send useful logs

Include the Saved/Logs/ file when reporting through the official Discord.

SOURCE MAP

How the guide uses the collected material

Official EA listing

Current version, scope, controls, requirements, systems, known issues, and roadmap

Official feature videos

Followers, trailer, download guidance, Poké Ball catch improvement, and progress updates

Community walkthroughs

Opening route, interface observations, battle presentation, and player-facing setup

Steam Deck guides

Extract ZIP, add the Windows executable to Steam, use Proton Experimental, and adjust window mode

Open the 19-video research index +

FAQ HUB

More detailed guides

Use the visual reference above for a quick answer, then open a page for the full version-labeled explanation.