-
Notifications
You must be signed in to change notification settings - Fork 167
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
Bi-directional communication with PogoLocationFeeder #225
base: development
Are you sure you want to change the base?
Conversation
#138 add PlayerDelay to Evolve task
do you know the muffin man?
This reverts commit ade0d4c.
corrected RazzBerry Name and added German Line for Not enough Pokemon for lucky egg.
Corrected RazzBerry Name and added German Line for Not enough Pokemon for lucky egg. in translation.de.json
…into snipe-both-ways
@eslindsey Actually your PR got somehow filled with stuff lol We need to verificate this if we really want our bot to send actually data from users. |
prob a good option to make it possible to toggle this future on/off in order to account for DurtyFree's input |
The option to turn it on/off already exists in PogoLocationFeeder...do we need/want a redundant one here? |
I don't think we would need a toggle, as long as failing to send a message doesn't cause lag or a crash. |
Lets the bot send encounter data back to PogoLocationFeeder, which can be configured to relay them to the feeds using PogoLocationFeeder Pull Request 42. This essentially allows instances of the bot to be turned into coordsbots.