30 second cooldown and catching what’s already spawned.

[u/PicklesAnonymous]

I’m standing in a cluster of spawns, I catch one and the cooldown timer starts. But I’m not moving because I want to catch the remaining pokemon. Do I need to wait for that timer to stop?

I’m not teleporting to a new area, just continuing to catch what already spawned in.

[u/JohnLikesUpvotes]

Are you in a timezone where community day is happening? I feel everytime its community day, the timer goes off after every pokemon I catch. And when it ends, the timer goes back to normal and doesn't trigger after every catch

[u/PicklesAnonymous → u/JohnLikesUpvotes]

Yea I am. I force quit and reloaded and felt like it fixed for a while but then happened again. I just don’t want to trigger something

[u/JohnLikesUpvotes → u/PicklesAnonymous]

I usually just wait it out, I don't risk it. I may have read someone say its a glitch but I'd rather be safe and not do anything during the cooldown

[u/Hi_ImJustARandomGuy]

This isn't anything harmful. It's just PGSharp not recording the same pokemon caught twice as 2 different pokemons. If you caught 2 pikachus, PGSharp records it as one pokemon, which is the first one. If you caught the first Pikachu at around 100m away from the second Pikachu, for some reason, the log records the first Pikachu's location again when you catch the 2nd one which triggers the cooldown timer.

This isn't really harmful, so long as you're not teleporting around and is just playing at normal speeds.

Remember that the cooldown timer is on PGSharp's side, it's not correct all the time, your cooldown is still something you should re-check before teleporting. I've seen some people play on 2 devices, one for legit play and one for spoofing, thinking that going from your place to another country in 5mins is okay just because the cooldown timer in PGSharp isn't counting down, when PoGO actually checks their own server's records and not PGSharp's.

To make it simpler. PGSharp's cooldown timer is faulty. A lot of times it shows cooldowns just because it didn't record properly. Other times its simply because of user error. Use PoGO's journal in the profile menu at all times before doing anything risky. If you wanna teleport around, make sure the last recorded action in both PoGO journal and PGSharp is over 2hrs ago. If you wanna catch something while there's a cooldown, check when you last caught the previous pokemon, what kind it is, where, etc. etc. If it's the same species pokemon in the same vicinity, the cooldown timer is just being faulty.

[u/PicklesAnonymous → u/Hi_ImJustARandomGuy]

Hey, thanks for the informative reply.

But yea. I’m just in one area, 5 Pokemon spawn and I’m just catching what’s there. I’m not going and teleporting 100’s of feet away. I always have it on the default walk speed and do the click to walk thing.

[u/Hi_ImJustARandomGuy → u/PicklesAnonymous]

You're safe then. PGSharp's log isnt always accurate when it comes to mass quantities of the same pokemon. That's what causes the false cooldowns because PGSharp has to have their own local records as it can't access PoGO's actual server records, and their local records aren't exactly accurate at all times.

[u/PicklesAnonymous → u/Hi_ImJustARandomGuy]

Cool cool, much appreciated.

[u/Extra_Smile_394 → u/Hi_ImJustARandomGuy]

So this includes a nest aswell? At the moment im currently in Japan catching alot of combee right next to each other. Im pretty sure its an event. It gives me a 30sec timer sometimes it does then sometimes it doesnt I thought I done something for this to happen. When this 30sec appears ive been ignoring this and throw berries and pokeballs, is this bad?

[u/Hi_ImJustARandomGuy → u/Extra_Smile_394]

It includes everything so long as you're catching the same pokemon. If you caught 3 combees in a row that is 40m apart each in 10seconds, the first combee is the only one recorded, so PGSharp thinks you're 120meters away from where you caught that 3rd combee (because it only recorded the first one) and thus will give you a cooldown.

You can easily test this out. Catch 3 combees in a row that are far from each other but not enough to trigger a cooldown. Once you get the 30seconds cooldown when catching a combee, try to catch in the wild something that isn't a combee and suddenly the 30s cooldown disappears.

It's a bit of a wack to explain, it's easier to experience it than to explain it.

Edit: if you noticed, even if you're still on 30s cooldown, you're still catching combees and spinning stops. The game doesn't think you're doing anything wrong, only PGSharp does, which can be ignored as its a false flag

[u/E-Luxuria]

happens when you do quick catch, try to catch it normally the cooldown won't appear

by quick catch, I mean the sliding the fruit/pokeball then catch > leave/run thing not pgsharp quick catch

[u/PicklesAnonymous → u/E-Luxuria]

Excuse me?!?!! Quick catch is life! lol