Several new types of bans have been implemented by Niantic over the past couple of weeks - bans that come from developer innovations running a bit too deep for their liking. The "if this then that" of these bans suggest that they're aimed at automatic bots - the bane of legitimate Pokemon GO gamers everywhere.
1. Pokestop over-use: Users will be banned when they tap and spin around 2-thousand Pokestops within a single day.
2. Pokemon over-catch: Users will be banned when they catch over 1-thousand Pokemon in a single day.*
*Even if a user caught one Pokemon every 5 minutes without fail for a full day, they'd only be capturing 288 monsters total. For a real user, catching 1,000 Pokemon in a single day isn't actually possible without cheating.
The same goes for the Pokestop over-use rule - a user would need to spin more than one Pokestop every single minute for a full day to get anywhere near the 2-thousand spins mark. That's just spins that produce loot, not the same Pokestop over and over again, one immediately after the other.
3. Too many accounts on the same IP: A user should not, under any circumstance, be running more than a single Pokemon account from their phone (or other nefarious devices) at once. Users will be banned when 3 or more accounts are running at once on the same IP - unless they're just standing around doing nothing, or just hatching eggs by walking.
4, 5, 6, etc: There were already plenty of reasons why an account would be soft or hard-banned from Pokemon GO, including but not limited to: GPS coordinates/ server requests from 100's of miles away made within minutes of one another, being caught (through various means) using a "bot", attempting to access Niantic's Pokemon GO servers through non-sanctioned means, or using a modified/hacked version of the Pokemon GO app file.
Dann denkst du ernsthaft das du damit durch kommst die haben doch bestimmt eine schön aufgeräume Datenbank ohne die würde sowieso nichts laufen und wenn sie dort einfach nur control+f drücken und level 40 oder sowas eingeben und danach backspace hat sich die sache schon gegessen.
