edit: nvm, found my problem.
edit: nvm, found my problem.
Last edited by Sidelancer; 07-05-2012 at 07:12 PM.
edit: I'm a giant noob. Again. Wrote "chest" instead of chestarmor. Works like a charm now.
Last edited by Sidelancer; 07-05-2012 at 07:30 PM.
So do you guys just run these 24/7 until you get banned? Or shut it off every once in a while so it's not so obvious? Is there a difference?
Hum...Really anxious about whether this will be banned or not...Currently use gold bot may be safe for me almost 20hr per day. But run this...Hum...still waiting.
Tomed, Could you share your experience that how long you run this bot for one day? And how many days have you run before?
As far as "the better way" goes as to programming one. I just finally got mine to work with the new way, testing input limit atm...
Lately it's been very sporadic because I'm spending most of my time testing new features/fixing bugs and don't have time to bot/sell items. Right now I've been botting for about an hour at 500-1000ms search intervals with 20ms click delay and haven't received any input delay errors. 8 items have been found so far from my item config and I've had 0 "bad" buyouts.
I've only just got this bot fully working about 5 days ago so and I haven't been banned for using it yet but that doesn't mean that I won't. I may have just missed the previous banwave and will get hit by the next one. If you are going to bot Diablo 3 with ANY bot I always recommend using a second account.
The truth is, no one but Blizzard knows the exact parameters that result in you getting banned for AH botting so no one can really say that any bot is 100% safe. We can make some assumptions, however, like that spamming the AH every 200ms will most likely result in your account getting flagged. My bot gives you the tools to slow it down as much as you want, it's up to you how much speed you want to sacrifice for account safety.
Last edited by Tomed; 07-05-2012 at 09:11 PM.
Are the default speed settings "safe" (relatively speaking of course) ? I assume by 200s you mean the actual search speed (which is set to 1000-2000 on default).
The bans were handed out due to the amount of searches on an account. People that didn't bot 24/7 full bore were able to get their accounts reactivated. Other players over x amount of searches (inhumanly possible) were told to gtfo.
I made a ticket and their reply was "There is no way you stayed up for 3 days straight and maintained 4000+ actions per minute"
That was their response to my 3rd ticket, first two were automated.
Bans were handed out based on queries, faster the bot = more queries = more bans.
Random anything doesn't matter, people (myself included) had everything randomized.
Sample:
People with 3.5 seconds+ per search (from what I have seen so far) have been safe, a normal person can do it in about 1 second.Code:Loop { Random, x0, 186, 192 ; Random X start drag Random, y0, 447, 457 ;Random Y start drag Random, x01, 229, 231 ; Random X end drag Random, y01, 447, 455 ; Random Y end drag Random, x1, 106, 220 ;Random Range X for Search Random, y1, 487, 500 ;Random Range Y for Search Random, x2, 264, 738 ; Random Range X for Item Select Random, y2, 197, 217 ; Random Range Y for Item Select Random, x3, 618, 734 ; Random Range X for Buyout Random, y3, 507, 525 ; Random Range Y for Buyout Random, x4, 294, 392 ; Random Range X for Buyout Confirm Random, y4, 417, 439 ; Random Range Y for Buyout Confirm Random, x5, 356, 454 ; Random Range X for OK Random, y5, 273, 297 ; Random Range Y for OK Random, s1, 300, 350 ; Random Sleep Time
This bot is a cool concept, but if you abuse the piss out of search frequency, you WILL be banned.
Edit: I don't know if it even matters anymore, with input limit, that may be how they "fix" it.
Last edited by dra1985; 07-05-2012 at 09:43 PM.
The default delay values I provide are optimized so that the bot has a fairly good chance of working on most computers. Due to the nature of how it selects stats, the bot's performance is heavily dependent upon system performance. For example the bot will scroll down the list of attributes very quickly if your click delay is, say, 20ms. If your D3 client is not running fast enough it will miss a scroll and select the wrong stat. To truly get the fastest speeds your client should be running at 100+ FPS at all times and you should have fairly low latency to the server so that queries get returned quickly.
I will never make any claim that the default values, or any values for that matter, are "safe" to use nor will they prevent you from getting banned.
Last edited by Tomed; 07-05-2012 at 09:48 PM.
Does this bot provide a way to extract a certain set of info I need from the AH?
ie: I want to see bid and buyout prices of all 1h with strength, crit dmg, loh, chance to immo and vitality. Can this bot deliver reporting like this?