[Enhancement] Check timestamp before teleporting back to previous location after sniping.

[abhinavagrawal1995]

Short Description

After the bot finds a pokemon worth teleporting to, it teleports back to the player's current location immdiately afterwards. I faced a connection error (due to my internet) AFTER it teleported to the pokemon, but BEFORE the bot was able to go back to its initial location. Naturally, when my connection was restored it resumed and teleported back to the location.
The downtime gave the pokemon servers enough time to record my player's location and two huge jumps 15 minutes apart earned me a soft ban.

Possible solution

Record the timestamp before teleporting to a location.
Before the bot teleports back to its initial location, check that timestamp. If its more than some predetermined time interval, either pause the bot to prevent soft ban or take some other prevention measures.

[YvesHenri]

There are 2 sniping tasks, which one are you talking about?

[abhinavagrawal1995]

I'm talking about MoveToMapPokemon. But I guess this suggestion is applicable to all sniping tasks.
The basic idea is to make sure that the teleporting back and forth are both done instantly, and not minutes apart.

[Gobberwart]

Are you positive that's what caused the softban? I wouldn't think so, otherwise we'd all be getting banned every time we teleported.

[YvesHenri]

@abhinavagrawal1995 Teleporting (read CHANGING positions ONLY) does not cause bans, at least I NEVER heard of it. You can freely move around (change locations) for as long as you do NOTHING else (no catches, no spins, NOTHING). You've been banned very much probably of something else. I'm closing this. Please reopen if need be.