Stuart Travers

Suggest move "catch" out of MoveToMapPokemon task, and add new "priority" global config item to replace it. That way it could be shared by different tasks. Alternatively, could just prioritize...

Re api calls.. In an ideal universe the bot would only call the api when absolutely necessary, ie. To perform an action for the most part. As far as things...

I've just submitted a PR which goes some way towards refactoring to reduce api calls. Metrics and UpdateLiveStats now share the same cached inventory information (note that "inventory" from an...

Removed another api call from incubate_eggs. As far as I can see, GET_INVENTORY is now only called as part of inventory_refresh, which is called by heartbeat. Everything else should just...

I can see users ending up with tens (if not hundreds) of fragmented config files for different things, and I'm not sure this is really an improvement over monolithic configs....

Perhaps we could allow configs to be cumulative, eg. we have config.default.json (or a set of files) which are values we think are safe to use. User could then specify...

@mjmadsen Good idea mate. Could we make use of this (or something like it): https://github.com/lobocv/crashreporter

so... config.default.json = basic common settings that should work for everyone at a simple level advanced/config.whatever.json = configs for different tasks/options etc. that could be cumulatively added by "advanced" users

@mzorzy subdir per bot could get complicated to maintain. Then again, if you are capable of running multiple bots with multiple configs, you should be able to cope :)

Exactly. Bot can load multiple config files (passed from command line) and process them in the order received. Eg. python ./pokecli.py -cf configs/defaults.json -cf configs/sniping.json -cf configs/evolveall.json Loads defaults from...