What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Got banned in 2.0.3

Have you ever taken extra steps to protect yourself Kevin?

Like changing routes up daily, running 100% unique profiles or changing process names every so often?

Just curious
 
no
no
no

no extra steps
but i dont use Apoc D3 starter and dont run Battle net application, only for updates
 
whats apoc d3 started?
and how do u not use battle net application. I tried deleting it but it forces me to redownload it and open diablo 3 through it...
 
Wazaki - create a shortcut of diablo 3 and add in -launch in the shortcut properties.

Edit: d3 apoc is a setting you can turn on/off if using YAR
 
where do you write down -launch?
Im in the properties of the shortcut. Other than the "comment:" box i dont see anywehre else to write something down?
 
"D:\Program Files (x86)\Diablo III\Diablo III.exe" "-launch"
 
Botting on 1 account about 8h a day in past 2 weeks, all fine.

Anyway... Virtual Machine, v-p-n or prxy, changing processes, using bnet app or not... IT DOES NOT MATTER.

Most of the warden is embedded in battle.net.dll file. It scans the Diablo III.exe and other processes that are attached/injected into it. So there is no a single "safeguard" like few above that will prevent the warden seeing your bot except doing a 'double game whammy' where you make second instance of the game on top of the original. That is the protection that works 99.9%.

Like many people suggest, it is good practice not to let it do 100 games/h and similar precautions but that will only help you because if warden locks onto DB process or someone in blizzard notices weird account behavior, you are likely gonna get smoked.
 
lol this is a bumped post, had me stressin for a second. Lol
 
Botting on 1 account about 8h a day in past 2 weeks, all fine.

Anyway... Virtual Machine, v-p-n or prxy, changing processes, using bnet app or not... IT DOES NOT MATTER.

Most of the warden is embedded in battle.net.dll file. It scans the Diablo III.exe and other processes that are attached/injected into it. So there is no a single "safeguard" like few above that will prevent the warden seeing your bot except doing a 'double game whammy' where you make second instance of the game on top of the original. That is the protection that works 99.9%.

Like many people suggest, it is good practice not to let it do 100 games/h and similar precautions but that will only help you because if warden locks onto DB process or someone in blizzard notices weird account behavior, you are likely gonna get smoked.

What is a double game whammy?
 
It creates 2 of the game instances of 1 process. It is redirecting game code execution flow to a new copy of the game itself so you can freely edit this new copy while keeping integrity of the original one which Warden is scanning clear.

It is usually done at login screen before all warden modules are loaded. Blizz knows this and they now directly login you. This can be bypassed ofc but most people use bnet app so it can be a small hassle.

This is a example of MH running on the concept: http://i.imgur.com/GadNd9H.jpg
 
It creates 2 of the game instances of 1 process. It is redirecting game code execution flow to a new copy of the game itself so you can freely edit this new copy while keeping integrity of the original one which Warden is scanning clear.

It is usually done at login screen before all warden modules are loaded. Blizz knows this and they now directly login you. This can be bypassed ofc but most people use bnet app so it can be a small hassle.

This is a example of MH running on the concept: http://i.imgur.com/GadNd9H.jpg

So how can we do that? Is there a tutorial or guide?
 
Can any one tell me, if you suddently get banned, is it only diablo3 on your account that gets banned or is it all the games attached to the account ? (wow, d3 , starcraft ect. )
 
Is there a way to change the DB process name and description from the task manager? Maybe that way if Warden takes a screenshot it will be "hidden".
 
Back
Top