Added feature to reset coords based on distance and time last run #452
Conversation
# Conflicts: # PokemonGo.RocketAPI.Logic/Logic.cs Resolved using kdiff3
Fixed bug with lat long
|
Merged with latest master and reviewed Logger merge |
|
conflicts :) |
# Conflicts: # PokemonGo.RocketAPI/Client.cs # PokemonGo.RocketAPI/Logger.cs Resolved merge using kdiff3
|
Resolved again |
|
So what exactly has been added? |
|
When the program is first run, if the user could have traveled realistically back to the default location from the last known location, it deletes the coords.ini file so the logic will start from the default location. |
|
The code essentially looks and says if (distanceBetweenDefaultAndLastKnownLocation/timeCoordsLastUpdated) < 80kmph), start at the default location, otherwise continue from last known location and continue as normal. |
|
I have tested it with the latest merges and it works |
|
The point is, I (and someone who submitted an issue) like to start from the default location because there are several stops right there. If I haven't run it in a while, I want to start from that default point where there are several stops, not somewhere else. |
|
I do want it to venture out from there though and not set too small of a max travel distance because all that area has is pidgey and ratatta. lol. |
|
seems like a great feature to me |
|
This is the stupidest 'realistic' idea ever. Nothing says "not-realistic' than always starting at the exact same spot every time. If this is kept, it definately needs to be a user config with defaulting to off. |
|
It's not a realistic feature, it's a start over without deleting the coords file feature... |
Added feature to reset coords based on distance and time last run
Also fixed bug with log causing crash in master branch