I think I follow what you are saying but I do find this discussion confusing because I think terms are being mixed &/or finer points glossed over in the thread... To try to be a little more explicit I will try to build on your statement as follows: A big part of the problem is the terminology Blizzard uses (and therefore we are using) is not precise and thus people are confusing things... To properly digest the usage scenarios both we and Blizzard should use proper terms as follows:
To be clear then we should then break things out explicitly:
- Software automation of keys (like AHK scripts that control your character when you are AFK): Bannable;
- Hardware automation of keys (like a robot pushing the keys for you over and over): Bannable;
- Software Repeating of keys (1 human input, like holding a single key down, to let it keep doing multiple actions): Bannable;
- Hardware Repeating of keys (like the above but from a hardware level): Bannable;
- Software Unicasting to 1 client via MultiCast capable software: Now Bannable because the software can be abused;
- Software Multicasting or Broadcasting to 2+ clients: Now Bannable as that is the abuse they are trying to stop;
- Hardware Unicasting to 1 client: ALLOWED AND REQUIRED or we can't play with conventional IO options;
- Hardware Multicasting or Broadcasting to 2+ clients: Is a GRAY AREA that isn't specifically called out in the recent ToS change (yet) but some Blizzard Representatives have explicitly clarified that it is NOT allowed while others have given conflicting guidance or won't answer the questions... Some Multiboxing advocates have discussed that neither hardware multicasting nor broadcasting is required to be a successful MultiBoxer and only puts our community in further jeapordy... They have also shown configuration examples where a multicast hardware setup can effectively be made into a unicast setup by binding a key only in 1 client such that all other clients receiving that key ignore it because it isn't bound...
Connect With Us