Is it possible YAR is responsible for the recent bans?
Since DB is not detectable, YAR, as a standalone, sure is.
im using 0.2 atm, when db crashes 3 times in a row, yar closes db and d3 and status is "Standby"
the status will be like that till i manually start the bot again
how should it work? anyone else got the issue with bot staying in "Standby" modus ?
Please think before you type. DB and YAR are in the same boat as far as Blizzard is concerned. Actually I take that back, YAR would be more classified in the realm of ISboxer as far as Blizzard sees it, it in no way interacts with D3 like DB does. So if DB is not detectable (and even if it is), YAR surely is NOT either.
People had been banned en-masse before for using auto-it scripts that only did pixel reading.
I'm not looking for uninformed opinions of what qualifies as "interesting" to Blizzard, or what they "could" scan for.
I'm looking for a concrete answer whether warden scans for YAR, thus making it one of potential reasons behind the recent bans. Thanks in advance.
P.S. Remove the first sentence in your post and you will come off a less of an internet cowboy. For future, mature, reference.
Same problem here. I cannot start another Bot instance (no more than one).I have a problem ... to crank or start the second bot .... not boot and the screen turns gray .... someone can help me ... plssssssss