Transfer Ttimer

[FoxBox]

The timer that used to exist between an action and transferring a Pokemon no longer exists. No matter if it's an evolve or a catch, the transfer is immediate, and THEN the timer counts down. Perhaps it's the timers for the things before the transfers then, but something isn't right.

View attachment 2016-12-22_T01_05_00.txt

Edit: Actually even between transfers there is sometimes little or no pause, so it could just be the act of transferring itself.

 

[Tony]

we will check it asap

 

[FoxBox]

Another transfer issue, if "transfer immediately" is not selected it will not transfer Pokemon when the Pokemon count becomes full. It'll just walk around.

 

[FoxBox]

The main problem seems to be between catching a Pokemon and transferring it. That seems to be an immediate "transfer RIGHT after catching" type thing. For example:

[04:52:44] Caught Rattata CP(10) IV(69) successfully.
[04:52:44] Received 110 EXP.
[04:52:44] Received 100 stardust.
[04:52:44] Received 3x candy.
[04:52:45] Transfered Rattata with CP(10) IV(69) successfully.

[04:50:36] Caught Bellsprout CP(359) IV(20) successfully.
[04:50:36] Received 150 EXP.
[04:50:36] Received 100 stardust.
[04:50:36] Received 3x candy.
[04:50:37] Transfered Bellsprout with CP(359) IV(20) successfully.

[04:54:23] Caught Rattata CP(162) IV(58) successfully.
[04:54:23] Received 160 EXP.
[04:54:23] Received 100 stardust.
[04:54:23] Received 3x candy.
[04:54:24] Transfered Rattata with CP(162) IV(58) successfully.

[04:54:40] Received 3x candy.
[04:54:42] Transfered Pidgey with CP(238) IV(38) successfully.
[04:54:43] Looting Square Clock
[04:54:44] Received 50 EXP.
[04:54:44] Received item 1x Pokeball.

There's just no pause between certain things before and after transferring. In places like that last example where there's at least some pause between a catch and a transfer, there's then no pause before the transfer and the next action. There's either a pause before a transfer or after it, never both.

 

[FoxBox]

This still happens after the .166 update.

 

[FoxBox]

This is still an issue. Apology for so many posts in a row. The bot will catch, transfer or evolve immediately, if it evolved then it will transfer immediately if you have that rule set, then does all the waits.

 

[ssrpengel]

The issue seems to be that the order of the actions and the delays is wrong. What happens now, and has for several versions, is that catch, evolve and transfer occur immediately following each other, THEN the delays occur all together, one is now 15 seconds and one or maybe two are 5 or 10 seconds, and these delays all happen AFTER the actions.

So I think the bug is that the delays need to be put back in between the actions, rather than lumped at the end. There used to be a delay between the catch and the transfer but the order was messed up a few versions ago, maybe when the logic rules and evolve were added, I don't quite remember.

Depending on how things are coded, it seems like each action including each catch attempt, should have a delay BEFORE the action and in the same code block as the action so it's never separated or ordered a different place than the action, just like a user would need to navigate and scroll and choose another type of ball or reorient the device if they missed, etc. The delays should have some randomness about them, some longer some shorter, but the shortest still realistically long enough for a user to have done the action.