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

MoveToMapPokemon- snipe_high_prio_threshold not working #5224

Closed
crvfts opened this issue Sep 5, 2016 · 5 comments
Closed

MoveToMapPokemon- snipe_high_prio_threshold not working #5224

crvfts opened this issue Sep 5, 2016 · 5 comments
Labels

Comments

@crvfts
Copy link
Contributor

crvfts commented Sep 5, 2016

"snipe_high_prio_threshold": 799,
.... etc
Eevee: 666,

"type": "MoveToMapPokemon",
        "config": {
          "enabled": true,
          "address": "http://localhost:5010",
          "max_sniping_distance": 333,
          "max_walking_distance": 333,
          "min_time": 240,
          "min_ball": 5,
          "prioritize_vips": true,
          "snipe": false,
          "snipe_high_prio_only": true,
          "snipe_high_prio_threshold": 799,
          "mode": "priority",
          "map_path": "raw_data",
          "walker": "StepWalker",
          "max_extra_dist_fort": 10,
          "update_map": false,
          "snipe_max_in_chain": 21,
          "debug": false,

I've noticed for awhile now I have to either comment-out a Pokemon or delete them from config completely. Any ideas?

min_time also appears to have no effect. Sometimes bot will reroute to more desired pokemon when they only have a few seconds of spawn-time left.

@oralunal oralunal added the Bug label Sep 6, 2016
@mjmadsen
Copy link
Contributor

mjmadsen commented Sep 6, 2016

If you set eevee to 666 with a threshold of 799. you'll only walk towards the eevee, not teleport

@crvfts
Copy link
Contributor Author

crvfts commented Sep 6, 2016

I have config set to only walk. Pokemon are sought out in descending order as intended just fine, the only issue is that Pokemon that should be disregarded are still walked to. Am I simply misunderstanding how the task actually works or is it a bug?

@mjmadsen
Copy link
Contributor

mjmadsen commented Sep 6, 2016

For walking, all pokemon are hunted - I don't think ignore is applied, maybe wrong.

@crvfts
Copy link
Contributor Author

crvfts commented Sep 6, 2016

It worked fine for me previously without this issue. I tested some more this evening and after a couple hours, commented-out pokemon were finally ignored. It actually happened with Eevee and there was nothing else around within the walk range. Weird. Maybe it's an intermittent glitch? It seems when it happens it keeps happening for awhile and then stops for a day or 2. I only play in the exact same area all the time so it's the same pokemon day in and day out.

@YvesHenri
Copy link

I'm closing this as it might have already been fixed. If it isn't, please reopen a new one.

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

No branches or pull requests

4 participants