-
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
[ISSUE] "TransferPokemon" task broken #5651
Comments
Even if i start from a clean config, no transfer at all with 245/250 and
or |
Same error here: "type": "PokemonOptimizer", |
Just checked latest dev branch and transferpokemon is working as expected, given the rules I've supplied. @ChrisHaPunkt The default config does not release anything until you configure release rules (near the bottom). That's by design for safety reasons. I notice in your original config, you have specified to keep a lot of things. That is cumulative, so perhaps your bag is full of things you actually told the bot not to release, and it now can't make any more space? Hard to say without knowing what you actually have in your bag. |
Until recently, we had an issue with transferpokemon that meant things were being released when they shouldn't be. This issue was corrected. Perhaps your bot is now working properly and your rules need attention? Here's my output from transferpokemon and optimizer, both transferring correctly:
|
Thanks for your answers. As mentioned, I started also from a clean config with adjusting the release rule (any below 1 IV, but keep best 1 CP) and the task configured as stated in op. Can someone confirm that the task is actually working on latest master branch? |
I cleaned up the release part in my config and it works again. I cannot tell what exactly did the fix. |
Expected Behavior
current pokemon bag 250/250 -> Should trigger the Transfer Pokemon Task
Actual Behavior
Will be completely skipped, no log entries, nothing.
Your FULL config.json (remove your username, password, gmapkey and any other private info)
Output when issue occurred
http://pastebin.com/yr6u0BZZ
Steps to Reproduce
cant tell, seems to appear after my previous
setup.sh -u
. But my Bag wasn't full enough to trigger.Other Information
OS: deb9
Branch: master
Git Commit: fd49544
Python Version: 2.7.9
Any other relevant files/configs (eg: path files)
The text was updated successfully, but these errors were encountered: