Evergreen
Asking Good Questions: Getting Help from the Pokémon GO Community
Get better answers from other Pokémon GO players: what details to include, how to share screenshots safely, and how to judge the advice you get back.
The difference between a question that gets ignored and one that gets a helpful reply is usually a handful of details. Other players are glad to help, but they can't see your screen or guess your goals. Trainer Hub doesn't host a message board of its own; these habits work in any space where you ask other players for help, online or at the Gym.
Before you ask: a quick check
A minute of looking often answers the question outright, or at least makes it sharper.
- Check the game first. For anything about a current event, the in-game news and the event information shown in the game itself are the most reliable source.
- Search with the Pokémon's name plus your goal ("Machamp raids", "Great League Azumarill"). A recent discussion about the same Pokémon often has your answer; an older one shows what to ask about what's changed since.
- Brush up on the basics. The beginner guides on the Trainer Hub homepage cover CP, IVs and moves, which answers many first questions.
- Decode the jargon. If replies you've seen are full of abbreviations, our Pokémon GO glossary explains terms like IV, STAB and DPS.
Five steps to a question people want to answer
- Lead with the actual question. Put it in the first line, then add the background. People skimming a busy chat decide in a moment whether they can help.
- Give the context that changes the answer. Name the exact Pokémon, including its form or variant (Alolan, Galarian, Shadow, Purified and so on), and say what you want it for: raids, a specific GO Battle League league, or simply your collection. A Pokémon can be a great choice for one of those and a poor one for another.
- Say what you've already tried. "I restarted the app and it still happens" saves everyone a round of suggestions you've already ruled out.
- Share a screenshot, cropped. An appraisal screen or a move list answers a lot of questions at a glance. Crop it to the Pokémon, its stats and its moves; lower down, a Pokémon's page usually shows where and when it was caught, which nobody needs.
- Mention your general region when location matters. Event start times, regional Pokémon and some seasonal spawns can differ by location, so "I'm in Europe" or "I'm in the Southern Hemisphere" can change the answer. Your general region is enough; never your exact location.
What to include for common questions
| Question type | Include | Why it matters |
|---|---|---|
| "Should I power this up?" | Species and form, its CP and appraisal, current moves, whether it's Lucky or Shadow (both change the power-up cost), and whether it's for raids or PvP | Under a CP cap, the best individual for PvP is often a different one from the best for raids |
| GO Battle League team help | The league or cup, your three Pokémon with moves, and what you keep losing to | Advice depends entirely on the format and on the Pokémon you already have |
| "Is this a bug?" | Your device type and game app version, what you did step by step, what happened, and whether a restart changed anything | Others can confirm whether they see it too, which tells you if it's widespread |
| Event questions | The event name as the game shows it, and your general region | Details and timing can vary, and people may be answering from a different time zone |
| "Where can I find this Pokémon?" | Your general region, and whether you've checked if it's a regional | Some Pokémon normally appear only in certain parts of the world, though events sometimes make them available more widely |
Unsure how to read the appraisal? Our guide to reading your team leader's appraisal walks through it.
Vague versus useful: two examples
These are illustrative examples, not real posts, but they show how much a little detail helps.
- Vague: "Is my Machamp good?" Useful: "I have a Machamp with Counter and Dynamic Punch and a three-star appraisal. Worth powering up for raids, or should I save my Stardust?"
- Vague: "Why do I keep losing?" Useful: "In Great League I keep losing to teams that lead with a Water type. Here's my team and their moves. What could I swap in?"
Judging the answers you get
Community answers come from players, not from the game's developer, and even experienced players can be working from old information.
- Prefer reasons over verdicts. "Yes, because its fast move is one of the strongest of its type" is more trustworthy than a bare "yes".
- Check how old the advice is. Moves get rebalanced and events change from year to year, so an older discussion may no longer be accurate. For dates, bonuses or featured Pokémon, check the in-game news before you plan around an answer.
- Treat conflicting answers as a clue. Two people disagreeing are often answering for different goals, such as raids versus PvP.
- Be wary of replies that pull you somewhere else. If a helpful answer turns into a request to switch to private messages or open a link, stop there. Asking in the open also means more people can check an answer, and others can learn from it. Our guide to staying safe in Pokémon GO communities explains the common tricks.
After you get help
If a suggestion fixed things, reply with what you changed. If nothing worked, say so and add what you learned from trying, since that often prompts a better second answer. Where the space lets you, edit your first message or mark it solved so the answer sits next to the question.
Questions a community can't answer
Some problems only official support can fix, such as a purchase that never arrived or a login you can't recover. The same goes for a warning on your account. Other players can't see your account or act on it. Our guide to contacting Pokémon GO support explains the route. Whatever the problem, never post your password or sign-in codes publicly, however helpful the person asking seems.