-
Notifications
You must be signed in to change notification settings - Fork 121
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
Trainer #29
Trainer #29
Conversation
…re of a 'middle' out - long walk to the first for at the moment
@dmadisetti by the way the bot in question is only doing sorting of forts different, but needs adjustments. I've made it use a quadtree to do some Z traversals, but I'm not quite sure how I could have it go "middle-out" rather than walking a kilometer to the first (and farthest) fort to start its run... after that the average distance is a little nicer than with the sort: |
@dmadisetti oh hell yeah, from an average of 415 meters to 155, all without my stupid quadtree! |
I like it. Will work out merge res problems |
def findClosestFort(self): | ||
# Find nearest fort (pokestop) | ||
logging.info("Finding Nearest Fort:") | ||
return self.sortCloseForts()[0] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
self.sortCloseForts() can be Null
…prehensible error. fixed another error when you have no balls of higher tier but had some at some point.
fixed it by throwing a better error. |
@dmadisetti care to have another look at this one? |
The cut average walking distance commit, really works well! |
see #86 |
Hey,
Haven't fully tested this (there could be a "self" that I missed), but it seems like a good idea to wrap all those loose functions into some logical entity.
I had mindlessly copied demo.py to a bot file, but it made it so it couldn't benefit from the changes you made. Now my own bot (I'll PR it when it works, if you want it in) can inherit from Trainer and and sort forts its own way!