-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Get lineup from Rocket Stops #1265
Comments
I believe this is different per player, or at least it was when they first got released. Feel free to test if this is still the case |
Lines up are not different, the mon you actually catch is random (from 1/2 slot, depends on type). |
While a grunt is active it's lineup will be the same for all players. The encounter can be randomly picked from slot 1 or 2, depending on type, like Jab said. But sometimes the encounter is guaranteed to be the first pokemon from the lineup. You can see info on which slots/pokemon you can encounter on the Silph Road site (pokeball means possible encounter slot): Sometimes it's really difficult to find a grunt with a specific pokemon in the first slot. Like right now the fairy type first slot can be Snubull or Ralts, if the lineup starts with Snubull I don't want to travel to that rocket stop. I've looked at about a dozen fairy rocket stops this past week and have only encountered Snubull. Having it scanned ahead of time will let me know if it's worth traveling to that stop. |
I've heard that clicking the "Battle" button on a Rocket Stop can provide the 3 shadow mons that you'll encounter. Can we add this capability to MAD? This would be a huge help in searching for specific shadow mons. And, it would save front ends from having to manually update lineups.
Also, if the account has a Super Rocket Radar, could we add the ability to detect decoy's? I know this will probably be harder to add, so maybe we could split this out into a future Feature Request?
This could be a standalone scan mode, or maybe it could be an optional (on/off) part of a raid scanner? Either way, thanks for considering this request.
The text was updated successfully, but these errors were encountered: