Runtime Destination change though json.config file#1768
Runtime Destination change though json.config file#1768asaf400 wants to merge 6 commits intoPokemonGoF:devfrom
Conversation
|
👍 Great, just what i needed. Hope this gets merged soon. |
|
The work that @douglascamata is to use websockets to support manual intervention of the bot, such as changing location like this. It will also support all sorts of other configuration and being able to be manipulated by a web ui. My guess is that is the right generic approach for this, but I'll let @douglascamata provide his thoughts. |
|
@TheSavior Yes, I am aware of that, Note that my code includes 2 workers. 1st worker trying to parse the config json file each tick, 2nd worker is listening for changes in the bot's variable 'destination_location', and walks there with the walking speed configured for the bot, and also, because the way workers are 'working' by an array order, it catches pokemon along the way so this can be used regardless of the 1st worker So I can revise this PL, To include only the 2nd worker, so that @douglascamata can use it |
|
@asaf400 this merge is severly outdated. How do you want to proceed? |
|
@douglascamata How do we want to proceed with this based on the socket server? |
|
I Can rebase the changes to latest dev, and refactor the code to make it compatible with the new event log \ tasks which are the major changes made to the code since this PR. @douglascamata Unfortunately I Didn't get you're messages about the socket server explanation in time, Slack Deleted those PMs.. So if you could quickly explain those here.. |
|
Outdate, need close. Thanks for PR. |
Feature: Runtime Destination change though json.config file
New destination.json in config directory,
when it has a value, the bot will walk towards the destination (respects global speed)
Oprates like so:
Config File:
made get_pos_by_name a public function
Also made a PEP8 Fix for the Constants