jabbink
[Suggestion] Adding a scanning slave
Well, let me explain my thoughts:
Just imagine you have two accounts, a main one which you want to farm, let's call it FarmBot. And another account (let's call it ScanSlave) which you want only to scan the area for pokemon to catch.
ScanSlave would scan the entire area for pokemon at the fastest speed possible (this bot is not here to catch anything anyway, so we wouldn't care about softbanning it, it just needs to scan fast), and FarmBot would then pick which pokemon to catch based on config.properties criteria.
Having such a feature would really be nice, and it would also prevent having to move randomly from pokestop to pokestop and having less chance to encounter desired pokemon.
Sounds like a lot to implement. The point of the bot doesn't seem like it would care about what pokemon you catch. Just to get you as much xp as possible. If you are looking for specific pokemon then just set the bot coordinates to the location where a map scanner says a lot of them are and run it there.
Yes, that's usually what I do, but even when doing so, the bot just wanders from pokestop to pokestop and just catches every pokemon that crosses its path. It cannot search for specific pokemon.
And there has been some options implemented in the bot with recent commits to make it ignore pokestops and/or not capture pokemon. So why not extend this to catching specific mons?
To me farming is not only about XP, farming mons to find one with great IVs is also a good option and having it would save a lot of time searching manually.
I see the point of what this is supposed to accomplish, but I don't think it's worth the definitely huge task it would create. Why not just set yourself up near a nest for that Pokémon and set the speed to 0? Don't get me wrong, if this was implemented it would be fantastic. The huge problem with the slave you want is purely the amount of work needed for it
- need to add options in the config for a second trainer login, key, etc.
- need to have the slave move around the location of the bot through the entirety of the runtime
- slave needs to communicate with the bot when it finds a desirable Pokémon
- bot needs to change the path on the fly, making the path found uneditable (if the slave found another, the bot may just walk around the Pokémon it wants because of path changing)
All of this for a program that's simply meant to level for you. In my opinion this is too extreme of a task for the current aim of the program.
@Wartickler explicitly, there has been no statement as far as I know. However, just looking at the bot and some pull requests you get a good idea of what the mission is thus far. Auto-evolve, auto-popping of a lucky egg before evolve, etc have all been discussed. Catching specific Pokémon may become the aim at some point (not my liberty to say), but as for the current aim it seems like too huge of a suggestion.
