Android 台灣中文網

標題: 又是一波的大逃殺…你中槍了嗎 [打印本頁]

作者: paipai0130 時間: 2016-8-16 16:42
標題: 又是一波的大逃殺…你中槍了嗎
我是二個星期沒掛了
等級24今天一早gg
根本就不是一些人說的一天1000支
我看是有掛他就抓…
有掛就不怕抓
抓了就繼續掛
等開放交易那天
我們一起把寵交易到乾淨的帳號去吧
看你怎麼ban

Power By APK.TW

: 登錄/註冊後可看大圖

作者: f26874940 時間: 2016-8-16 16:45
恩....你不知道可以查交易紀錄嗎?
如果是掛~那一定會把所有接觸過的都審查!!
沒開發過遊戲也玩過遊戲呀...

作者: paipai0130 時間: 2016-8-16 16:49
[b]After rigorous testing for the past 24 hours using fresh accounts, I have managed to somewhat debunk some of the new ban types, anyone who is able to capture the packets with a "permanently banned" account receiving one of the two possible login errors, I would appreciate you to look into them.

Capture ban - this ban is a 24 hour time out affecting the catch of Pokemon only and returns the error "CatchFlee" when botting. I have found that after running the bot on 3 accounts for ~6 hours all of the accounts were banned between 1002-1011 Pokemon captures so is based on 1000 Pokemon catches within a certain time frame, my guess on this threshold is probably 12-24, I am going to be testing this by allowing some time before reaching 1000 captures after 12 hours have passed.

Pokestop ban - this ban prevent use of any pokestops for 24 hours. This again occurs similar to the CatchFlee ban, 3 accounts received it after looting 2021-2034 pokestops. Also confirmed to has happened just after 2000 by a few other users. Again I can"t confirm the exact time frame until this threshold is reset, but likely 12-24 hours. The overflow past the 1k and 2k marks for these is probably based on another variable or sheer luck.

Temporary IP ban - this ban prevents any MapObjects from being returned temporarily based on your IP address (Pokestops, Pokemon, Gyms). This occurs from too many accounts/requests on the same IP address at once and can last 10 mins - 1 hour which seems to be based on the severity.

Login errors:
•
Data not received from server: Unknown as to how this occurs, it is still happening to actively running bots, but accounts that were previously botted and haven"t recently been logged into have also received it so it seems to be related to a ban wave.

•
can"t find a reference to the other login error but it is worded differently to the latter mentioning "Player information" I believe: Unknown for occurrence again.

My theory for the login error bans is that they may not be intentional and encourage someone to log the requests being sent before this is received. The reason I believe they are not intentional is that it would be in their best interest to show an actual ban message rather than it looking like they are having server issues still. It may be that a certain feature has been disabled in related to a ban and so the data it needs at login is failing to be returned or if it is a ban then some data may not be accessible also leading to this error being returned, this would make a lot of sense rather than intentionally showing this to banned users on login.

Again, this needs thoroughly testing logging all the requests before this is returned.

Hope this clears up a lot and helps people to potentially avoid the bans.

Thanks to SLxTnT for running these tests initially, has helped a lot to work this all out.

Edit: according to /u/Tr4sHCr4fT the API is returning "Status=3" to all requests after the player data is returned from the get_player() function. Hence the data error as it isn"t receiving what it needs to be returned to function properly and doesn"t know how to handle it so errors out. Interestingly the only other instance of a status 3 being returned is when the ToS message is displayed for new accounts, which would suggest it is trying to return data related to the ToS (possibly ToS violation message). This is increasingly looking like a ban, with some PTC accounts being able to even re-create their accounts with the same username. Anyone who was able to do this will have probably had the second error I messaged referencing "Player information". I think they have added this and the next actual app update will have handling for it to show an account termination error window.

Edit2: Further observations from SLxTnT-
Pokestop ban:
- Occurs when you search roughly 2k pokestops in a 23 hour timespan.
- No bypasses known.

Pokemon ban:
- Occurs when you catch 1k pokemon in a 23 hour timespan.
- Potential bypass by throwing missing pokeballs 15-30 times. (I haven"t confirmed)

Both of these bans have the potential of being lifted every hour. After ever hour, if your total pokemon / pokestops in the last 23 hours is below the ban threshold, you"ll be unbanned. If you surpass that threshold, you"ll be banned again.

對了…我附上官方的留言請大家去看一下吧…不用在那外傳及誤傳

作者: maxphoenix 時間: 2016-8-16 16:52
我看到圖片後,被鎖的感覺都消失了...
請貼更多

作者: paipai0130 時間: 2016-8-16 16:54

f26874940 發表於 2016-8-16 16:45
恩....你不知道可以查交易紀錄嗎?
如果是掛~那一定會把所有接觸過的都審查!!
沒開發過遊戲也玩過遊戲呀... ...

所以才說開新的帳號來交易
至少他們也會沒理由要回吧
又不是偷也不是搶

作者: michaellee807 時間: 2016-8-16 16:58
我有攝護腺保養和灌腸的需求，可以請那個妹幫忙嗎....謝謝

作者: chanmaymay 時間: 2016-8-16 17:00
不理他一樣掛

作者: hiyasi 時間: 2016-8-16 17:00
Pokemon GO Hub 推測由於 Niantic Labs 公司偏向保守，未來《Pokémon GO》的交易模式會類似目前購買寶可夢幣（皮卡丘幣）的過程，一切都由後台主機主導運作，交易過程也比較安全，這樣的交易過程，玩家無法利用手機直接和朋友交換寶可夢，也少了些人際互動的樂趣。

沒那麼容易交易！

作者: windchen1 時間: 2016-8-16 17:06
應該是大家把狙來的寵

全部跟別人換.....

有種把那些手動的也ban掉.....笑Niantic不敢

作者: n02040007788 時間: 2016-8-16 17:23
想當神奇寶貝大師沒這麼容易!!!

作者: paipai0130 時間: 2016-8-16 17:26

michaellee807 發表於 2016-8-16 16:58
我有攝護腺保養和灌腸的需求，可以請那個妹幫忙嗎....謝謝

先生
請去醫院
記得帶健保卡

作者: paipai0130 時間: 2016-8-16 17:29

michaellee807 發表於 2016-8-16 16:58
我有攝護腺保養和灌腸的需求，可以請那個妹幫忙嗎....謝謝

先生
請去醫院
記得要帶健保卡

作者: as5508 時間: 2016-8-16 17:32
使用外掛多少有風險了
被鎖了就重練一隻加油不要難過

作者: bonsono33 時間: 2016-8-16 17:33
原來已經開超過兩個星期了.......

作者: Na-Nick 時間: 2016-8-16 17:37
有幾個號還存活兩周多的路過......

作者: edel 時間: 2016-8-16 17:48
真的如其他所說的,今天沒事的,不代表明天就沒事,
官方就是來場大屠殺,才能讓玩家想繼續玩,
但對於我們來說:殺了一個我,還有千千萬萬個我.
小號不斷衝.

作者: a78121418 時間: 2016-8-16 17:50
謝分享!!!
來用看看

作者: f26874940 時間: 2016-8-17 16:12

paipai0130 發表於 2016-8-16 16:54
所以才說開新的帳號來交易
至少他們也會沒理由要回吧
又不是偷也不是搶 ...

怎麼沒有理由...?
你拿外掛掛來的寶物
等同分贓罪
勢必連坐處分的
別把遊戲想的那麼簡單..

歡迎光臨 Android 台灣中文網 (https://apk.tw/)