-
Notifications
You must be signed in to change notification settings - Fork 8
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
FR : Different geofences for pokemon/raids/quests #25
Comments
There is currently no geofence for pokemon, only a route. You can (and many do) have very different pokemon scanning than the broader quest/fort area. Forts & Quests use the same fence in an area. I agree, by the way, that forts & quests should each have their own geofence - and that pokemon could have a different geofence if you are "pulling" a route rather than pushing the route in from koji which is the more common use case |
I see what you mean. What I mean is that you can only define a single geofence, and if you the "Get Route" for pokemon, forts or quests, this geofence will be used... Would be nice to be able to specify different geofence, and then associate them to pokemon/forts/quests so that clicking "Get Route" gets you a route for the right geofence... I have several areas for which I'm scanning wider for raids than for pokemon. |
Forts & Quests get routes for themselves based on the geofence. |
I don't use any Koji Integration from Dragonite as my fences do not match for mons. But koji is designed to handle creating route for child fences.. the integration in admin can't handle that... I agree on a separate fort fence, but rather useless for mon fences as you can have multiple ones... E.g. one of my dragonite areas has 23 mon fences |
Would be nice if it was possible to specify different geofences for pokemon, raids and quests... With of course a switch like "use pokemon geofence" if they don't need to be different... At the moment the only way to achieve that is to create different areas.
Thanks
The text was updated successfully, but these errors were encountered: