So much possibilities about how they work...
we should push someone to get hired in blizzard development team![]()
So much possibilities about how they work...
we should push someone to get hired in blizzard development team![]()
when u killed one enemy over 1000 times in 24 hours. u are banned 100%! u wont hold ur account for ever. u will get a ban in future for 100%! do not bot on ur main. bot 24/7 on bot account only and DO NOT care about bans, just bot as hard as u can to make profit. that is the way. idiots think if they are botting juts "sometimes" they wont get banned lawl
double post da shit cause of #111 last post lawl![]()
That's not true either, if you really want to be optimistic, Blizzard might decide low level botting actually BENEFITS their RMAH economy and have decided to stop banning anyone below a certain # of bots say less than 8?
But like I said this is just wishful thinking based on the fact Blizzard is realizing Diablo 3 is a bleeding player base right now.
A MUCH MORE REALISTIC VIEWPOINT IS to believe that they are going to begin ban waves after each new content patch (say buffed legendaries and PvP?) in order to reset botting as players flow into and out of the game during peak interest in it.
No matter what, if you are botting, Blizzard is considering banning your account.
Last edited by KgKris; 07-30-2012 at 09:25 AM.
I'm not going to quote but some of your arguements really makes me wonder.
You can't know for sure what Blizzard is monitoring, but one thing that is certain is that Blizzard can't ban all of the botters, as of now. This would affect the economy/population in a bad way for Blizzard, go figure. You can't claim that people that bot will be banned with a 100% certainty, since you don't know exactly what they monitor, how they monitor, and most importantly: You don't know who/how many they will ban. I think Blizzard has enough statistics to be able to choose from a good amount of "different" botters.
It's possible that they track games created per hour, it's possible that they track amount of Sarkoth kills per day. But even if they have a Warden as advanced as NASA, they can't ban all the botters out there. It sure as hell doesn't seem as Blizzard "queues up" people for banwaves, as there are many people who have botted 24/7 since day 1 without any issues.
Me and a few friends have been botting using private AutoIt scripts, pretty much 24/7 since early days of D3, with 17-20s open runs, 8.5s closed runs(Sarkoth). None of us are banned yet. Luck? Bot behavior? We will never know, because we don't work for Blizzard.
All we can do at the moment is to speculate.![]()
Last edited by KojL; 07-30-2012 at 01:06 PM.
Is it me or it's been a week since blizzard made a banwave ? what are they plotting ?
No speedhack, not even reading memory, or writing to memory for that matter. It was wishful thinking at first, yes, but now I've reached those times and might release the script in a few days. But not sure yet, as it would be on the radar. If it isn't already.
However, runs can be faster than mine, if using memory read/write(just check DB forums), not sure about pixelreading though.
Last edited by KojL; 07-30-2012 at 03:45 PM. Reason: Correction
In approx 5-6 days I will release the script to at least a few people. I'm on laptop atm and I don't got the newest version on this computer, but keep an eye on the "Gold Profiles"-forum if I decide to share it to the public when I get home. PM me for more info.
Some info about the script itself:
It's a script strictly for Demon Hunters, as I'm not playing any other classes, and it's based on another great script from OC. Open runs are approx 17-20s, depending on DPS, closed runs 8.5s. The script is using a Vault-setup.
I ran a stability test overnight, resulting in 510k GPH after 13 hours with no breaks, with 301% Gold Find. This is from pure gold drop, not counting any salvaging, vendoring or whatever.
HOWEVER, realize that I might decide to release it to a few people only, so please don't expect anything yet.
KojL
Last edited by KojL; 07-30-2012 at 05:45 PM. Reason: Added info on the script