Skip to content
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

Infinite loop when pokemon bag is full #3641

Closed
Setsu-BHMT opened this issue Aug 11, 2016 · 6 comments
Closed

Infinite loop when pokemon bag is full #3641

Setsu-BHMT opened this issue Aug 11, 2016 · 6 comments

Comments

@Setsu-BHMT
Copy link

Expected Behavior

Bot should ignore all pokemon when pokemon bag is full

Actual Behavior

Bot gets stuck tracking down lure pokemon it can't catch.

Your config.json (remove your credentials and any other private info)

Using a minimally modified example.json

Steps to Reproduce

Fill pokemon bag completely, then run bot.
Eventually it will encounter lure pokemon and get stuck.

Version

Latest Dev branch pull
Python 2.7.12 on Ubuntu 16.04

@Ph4i1ur3
Copy link

What would you propose the bot do? It sounds like you should adjust your config to release more Pokemon.

@Setsu-BHMT
Copy link
Author

@Ph4i1ur3 The bot should just walk and spin forts is a more reasonable thing to do.

Ideally I'd like a config setting for when the pokemon bag is full to do evolving or more aggressive releasing

@jrjhealey
Copy link

I have to say some kind of sensible handling of this would be appealing. Trying to finesse the config file to maintain a steady level of pokemon release/retain can be tricky, especially if you're new to the bot.

@fari-99
Copy link

fari-99 commented Aug 12, 2016

hmm, in old master bot, there is a mode for farm, catch and all. but in dev, it changed into a serial of a task we see today. what i can recommend now, just delete the catch pokemon task.

all = catch and farm (spin fort and catch pokemon)
catch = only catch pokemon
farm = only spin fort.

@Setsu-BHMT
Copy link
Author

@fari-99 True, but my point is the bot shouldn't need reconfiguration in order to deal with this issue.

@mjmadsen
Copy link
Contributor

This should be solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants