Re: Question: Possible work around from blizz's new policy?
![Post Post](./styles/acidtech/imageset/icon_topic_latest.gif)
At the moment I am thinking about a setup with viewports and become a mouseclicker. I hope "Bob" would be able to do this.
The world's top multiboxing software!
https://isboxer.com/forum/
bob wrote:Our workaround is to work on some software that does not have input broadcasting capabilities.
Raysix wrote:At the moment I am thinking about a setup with viewports and become a mouseclicker. I hope "Bob" would be able to do this.
rippx wrote:I just hope Blizzard doesn't begin detecting isboxer/lavish software.
rippx wrote:Perhaps the best pathway to take is open disclosure with the Blizzard dev team and tell them that isboxer is no longer an input broadcasting software so there is no need for warden detection.
rippx wrote:Also, I hope there is some way you can keep this a secret from the botters, I don't want them to steal the idea you would be working on and the multiboxers end up getting punished again.
fixitman wrote:Instead of guessing, I'm testing.
Prepared wrote:fixitman wrote:Instead of guessing, I'm testing.
You can test if you want to. But I already know what Blizzard is doing based on what happened to me. As the number 1 player reported by more than anyone in World of Warcraft, yes I'm proud to say that, I can tell you with 100% confidence how Blizzard is tackling this.
What they're doing is relying on player reports. If you use InnerSpace but get no player reports then you wouldn't receive a warning. If you launch the game with InnerSpace it doesn't matter if using keyboard broadcasting or not if someone reports you, you will get a warning. If you read the message sent to your email address it clearly tells you that you can't use Input Broadcasting Software that means you can't launch the game with it. Whether you broadcast the keys or not is irrelevant to them. That's the way it is right now. If you receive a warning I don't know what Blizzard will do after catching you again through player reports. Has anyone received a second warning or kept going to find out?