How we most likely get detected! Please developers FIX!

[LethrblakaGR]

So i my setting are to NOT trasfer Immediatly.
My PF keeps doing this fucking shit. Transfer one pokemon and then selects and transfer around 20+ pokemon in 1 Second between the first transfer and the second! Proof below.

 

[Qduaty]

You can do the same straight from original pokemon software you knobhead lol.,..

 

[Hananashk]

No, you cant in this speed. can you select 30 different pokes in 6 sec?

 

[odg250]

you do realize that if you long press a pokemon, it then allows u to select multiple pokemon by just clicking and then do a mass transfer right?

 

[leinifas10]

No, you cant in this speed. can you select 30 different pokes in 6 sec?

Yes you can, using the long press feature. Dude, do you even know how to play the game?

 

[mgiara]

Yes you can, using the long press feature. Dude, do you even know how to play the game?

Sure, but using the multi-transfer feature, long press, select 50-60 'mon, and finalize the transfer

All in 6 seconds?

My girlfriend would like to experience your fingers my good sir/ma'am

(I know OP said 20 but look at the photo..

 

[disarmwithsmile]

My girlfriend would like to experience your fingers my good sir/ma'am

lol

 

[Hananashk]

Sure, but using the multi-transfer feature, long press, select 50-60 'mon, and finalize the transfer

All in 6 seconds?

My girlfriend would like to experience your fingers my good sir/ma'am

(I know OP said 20 but look at the photo..

Exactly. So dudes please turn on your brain, before arguing. Long press on a poke = 1,5 Sec. 6 Sec between to actions (Transfer one and then transfer 30). Now imagine how long you need to SELECT the pokes... not to transfer them...

 

[trallkos2155]

Exactly. So dudes please turn on your brain, before arguing. Long press on a poke = 1,5 Sec. 6 Sec between to actions (Transfer one and then transfer 30). Now imagine how long you need to SELECT the pokes... not to transfer them...

You do realize that the presses, including long presses are most likely done and kept client side. If every single press you made, including selecting , de-selecting pokemon were sent to Niantic, that would be an incredible waste of bandwidth and a collection of a massive amount of useless data which would slow down the game for everyone. It's the final transfer that gets sent, and that is done within a few seconds in the actual game. Now I'm not an expert by any means , but I'm sure a dev with some knowledge could help corroborate this.

 

[Hananashk]

You do realize that the presses, including long presses are most likely done and kept client side. If every single press you made, including selecting , de-selecting pokemon were sent to Niantic, that would be an incredible waste of bandwidth and a collection of a massive amount of useless data which would slow down the game for everyone. It's the final transfer that gets sent, and that is done within a few seconds in the actual game. Now I'm not an expert by any means , but I'm sure a dev with some knowledge could help corroborate this.

I think we have to clarify this further:
Yes, you are right. The selection itself is client side. No data collected.
When sending Pokes it must be told the server, that you send something, right?
If you look in ops log: He send one at 17:58:41. The server (niantic) got this information.
6 sec later he send ~30-50. The server got the information that between 6 sec someone selected over 30 pokes.
That could trigger an investigation.

 

[char9527]

I think we have to clarify this further:
Yes, you are right. The selection itself is client side. No data collected.
When sending Pokes it must be told the server, that you send something, right?
If you look in ops log: He send one at 17:58:41. The server (niantic) got this information.
6 sec later he send ~30-50. The server got the information that between 6 sec someone selected over 30 pokes.
That could trigger an investigation.

Well, I support your inference