ThePunisher
New Member
- Joined
- Nov 22, 2016
- Messages
- 29
Yes you can ask for a refund if you purchased your key less than 7 days ago.
Send an email to [email protected]
Check email pls, i just send mine to refund
Yes you can ask for a refund if you purchased your key less than 7 days ago.
Send an email to [email protected]
No ban for me because I'm not stupid enough to use a product that has a reoccurring history of getting you banned.
Make's me laugh. I called this out 3 banwaves ago. You are all pretty dumb if you think you have any protection or chance of actually keeping your accounts. This is detected.
so why follow this community xDNo ban for me because I'm not stupid enough to use a product that has a reoccurring history of getting you banned.
Banwave was day 28 Jan, for sure..
How do I know this? easy.
Day 28 I created an account (bchest) and used the bot to level the account up to level 6 (delivery account). The delivery account has been suspended for bot usage. He used HB for two hours.
Day 29 I created a farmer and used the bot to level up to level 110. The account has not been suspended, and has used the bot until today.
Yes I am thinking this also. I made a new account on Day28 also, only used a manual combat routine on it so far (lv45 toon) and the account is banned. Day29 I made an account for professions...levelled herbs and mining all day and it's not banned. Only saving grace is I didn't attach the Legion key I purchased so I still have it....Banwave was day 28 Jan, for sure..
How do I know this? easy.
Day 28 I created an account (bchest) and used the bot to level the account up to level 6 (delivery account). The delivery account has been suspended for bot usage. He used HB for two hours.
Day 29 I created a farmer and used the bot to level up to level 110. The account has not been suspended, and has used the bot until today.
It seems that a new detection vector have been introduced in WoW 23420 patch that we -did- anticipated, but couldn't find and assumed it was fine.
I'm sorry to say that we were wrong.
A bit of history:
25th of October 2016: Blizzard introduce a new anti-bot detection in patch 7.1.0.22900.
11th of November 2016: First wave of bans hits all major bots.
22th of November 2016: Second (anticipated) wave of bans hits all "suicidal botting" users.
24th of November 2016: We found the detection vector and can trace it back to patch 7.1.0.22900.
24th of November 2016: We fixed the detection vector added in patch 22900.
3rd of December 2016: Blizzard introduce a new anti-bot detection in patch 7.1.0.23171
3rd of December 2016: We found the detection vector added in patch 23171.
3rd of December 2016: We fixed the detection vector added in patch 23171.
10th of December 2016: Blizzard introduce a new anti-bot detection in patch 7.1.0.23222
10th of December 2016: We found the detection vector added in patch 23222.
10th of December 2016: We fixed the detection vector added in patch 23222.
Somewhere in between: We found detection vector update in PTR patch for 7.1.5.
10th of January 2017: Blizzard introduce a new anti-bot detection in patch 7.1.5.23360
10th of January 2017: We found the detection vector added in patch 23360.
10th of January 2017: We fixed the detection vector added in patch 23360.
25th of January 2017: Blizzard introduce a new anti-bot detection in patch 7.1.5.23420.
25th of January 2017: Blizzard introduce an implementation of System32.ReadProcessMemory function. But after debugging for long hours, we didn't see any use of it and released as-is.
1st of February 2017: Third wave of bans hitting major bots.