-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Task Priority - Evolve vs Release #3416
Comments
This will be a great modification. Make evolve a Pokemon gives +500PX, so for the recurring Pokemons this is a lot of PX |
You need to swap the For example I have this
Which results in the following logs
|
That would be completely backwards looking from a Top-Down execution tree.... |
A better documentation of the task list would be really helpful, the wiki seems to be outdated anyways. |
@extink Thanks ! This is working for me. But my config file is different. See below :
|
Expected Behavior
Tasks are executed in order that they are listed
Actual Behavior
Evolve task is not given priority to release task
Your config.json (remove your credentials and any other private info)
Steps to Reproduce
With the task list above one would expect that the bot would evolve a pokemon before considering the release options. Capture happens, the task list is looped back to the start (after checks for FortSpin and FollowPath is updated) and the Evolve task is encountered before the Transfer task. This is not how it's currently working as it will capture a pokemon and then release it on the spot. This is leading to a major excess in candies being collected and is wasteful in terms of XP gain as 'trash' pokemon can be evolved for 12 candies and then thrown away if they're not worth keeping. If we don't have the 12 candies then the trash pokemon can be ditched to keep storage under control.
Additional Note: Hatched Pokemon get evolved before release. Only Captured Pokemon appear to be ignored.
The text was updated successfully, but these errors were encountered: