Change in multiboxing policy

[nodoze]

In addition to multiple reports of warnings from multiple people using ISboxer with any/all broadcasting turned off, we have the following message from the developer behind ISboxer and InnerSpace:

Update from Lax in the ISboxer Discord on 11/06/2020 at 10:31 AM:

"They are detecting Inner Space being used, and issuing warnings for "using software intended for input broadcasting". So it doesn't matter which features you disable."

https://i.gyazo.com/d9c0633a77957bc0690dab823cc16692.png

My respectful recommendation to everyone is to stop using ISboxer/InnerSpace with either Classic WoW or Retail WoW until we know more. Official announcements from Lax are typically in the ISboxer Discord's #announcements channel.

Lax is also working on a new "skinny" release of ISboxer/InnerSpace that will hopefully be compliant with Blizzard and hopefully officially OK'ed by Blizzard (may end up with a new name instead of ISboxer/InnerSpace).

[woloss]

Well, as I said, hyperspawn still gonna be a thing.
https://imgur.com/a/xSdvXVr
Looks like 107x accs w/o soft. So, ye

[nodoze]

Well, as I said, hyperspawn still gonna be a thing.
https://imgur.com/a/xSdvXVr
Looks like 107x accs w/o soft. So, ye

I don't see how that can reasonably be done via pure hardware without software.

How are all the windows sliced like that?
How are all the clients getting inputs?
How are all the clients launched and in how many OSes?

Bottom line is whatever they are doing is going to be looked at by Blizz and then likely Nuked so we should all be ready to BOHICA.

[woloss]

I don't see how that can reasonably be done via pure hardware without software.

How are all the windows sliced like that?
How are all the clients getting inputs?
How are all the clients launched and in how many OSes?

Bottom line is whatever they are doing is going to be looked at by Blizz and then likely Nuked so we should all be ready to BOHICA.

I don't know, but looks like he is using just 1 Windows 10. I'd better go with few VM's, due to lack of VRAM at least.

Windows sliced manually, probably combined with custom resolution through Nvidia Control Panel.

As for inputs, it's pretty simple, Windows 7 - 10 have workarounds. + some adjustments in-game. Main focus on mouse here.

[CokeZero]

It appears to me the whole reason for Blizzard doing what they did was to prevent bots from having such an easy way to "multi-bot" in the first place. Not as a direct attack on multiboxers themselves, just collateral damage that they can live with unfortunately. So any new means to try and skirt the software ban, but still ends up making it easily accessible to the botters, will be looked at unfavorably from now on.
If Lax is working on something that somehow prevents botting with it, great, I'm all for it and can't wait to try it. But if botters can still jump on the bandwagon and utilize it for scummy play, I don't have my hopes up for it. That goes for any workaround people come up with, if botters can easily do it to setup hundreds of accounts, you can pretty much forget about it. Blizzard will ban first, and let you try and convince them why they should reopen your accounts.

[nodoze]

I don't know, but looks like he is using just 1 Windows 10. I'd better go with few VM's, due to lack of VRAM at least.

Windows sliced manually, probably combined with custom resolution through Nvidia Control Panel.

As for inputs, it's pretty simple, Windows 7 - 10 have workarounds. + some adjustments in-game. Main focus on mouse here.

Even with 128GB of ram on my machine and a beefy processor I have a hard time seeing it done on 1 windows machine & VMs would add overhead.

Maybe on a threadripper or multi-cpu machine with more ram it could be done but I have had issues with pipelines and underlying windows infrastructure when going with more than 30 copies of games in the past (was only using about 70 of my 128GB of RAM but windows could not handle all the client interactions and the 8GB VRAM on my graphics card was not enough...

It may indeed be doable and if it is that sucks because folk like him/her will likely cause the other shoe to drop (or the next nuke which will ban hardware multi-broadcasting)...

[woloss]

Even with 128GB of ram on my machine and a beefy processor I have a hard time seeing it done on 1 windows machine & VMs would add overhead.

Maybe on a threadripper or multi-cpu machine with more ram it could be done but I have had issues with pipelines and underlying windows infrastructure when going with more than 30 copies of games in the past (was only using about 70 of my 128GB of RAM but windows could not handle all the client interactions and the 8GB VRAM on my graphics card was not enough...

He have 3970x with 256gb. With such weird resolution, must be fine with VRAM and so on. Well i did 16 chars on my 970 3.5GB in 3840x1575(or smth like this), in most cases its fine, for farm its way more than enough, for pve/pvp, not really.

Well, VMs won't add much overhead, plus even 3xxx AMD series have infinite fabric. In some cases you can divide clients to good CCX and so on(on 2990wx it gives better performance than native, but ye, not sure about 3xxx totally, they reduced infinite fabric involve).
On the other hand, with VMs you need to move two mice, rip wrists

[emmanuelfs]

Ok, so lets say someone finds a "legal" way around the TOS, do you think blizz is gonna take the time to investigate once you get reported? if they see a multiboxer, they see someone broadcasting keys, I dont think theres a way around this

[woloss]

Ok, so lets say someone finds a "legal" way around the TOS, do you think blizz is gonna take the time to investigate once you get reported? if they see a multiboxer, they see someone broadcasting keys, I dont think theres a way around this

Warden scanning your memory, so, I guess they know what are you using and make decision based on this. If you don't have innerspace/ahk/hkn in background, you must be fine.

[nodoze]

Warden scanning your memory, so, I guess they know what are you using and make decision based on this. If you don't have innerspace/ahk/hkn in background, you must be fine.

It is not that difficult for Blizzard to stop everyone from doing 1 action into more than 1 wow client for most scenarios.

Discussion on how to do this here:

https://www.dual-boxing.com/threads/...194#post433194

There are some ways to try to obfuscate and try to get around this... For example sending every wow client through something like a "TOR network" or to a different VPN destination and have each client login to a different server but even that could be tracked with the right analysis process of time/patterns.