No broadcast software ideas for multiboxing

[nodoze]

"1 input causing only 1 action in only 1 client" While I'm fond of this wording myself, Blizzard has never actually stated this is their new policy. That is our interpretation of their intent - and we don't all share that interpretation. So on one hand I agree with you, but we can't state that as a hard fact unless/until Blizzard clarifies their new rule.

@nodoze On the previous page we were discussing different ideas for keyboards and how they could be cobbled together to send multiple outputs based on 1 button press. You seemed to take offense to the idea of connecting the electrical wiring of the switches together to create a broadcast keyboard, but you're OK with the idea of connecting the physical switches together. I'm honestly not following your logic on why you think electrical connections are bad, but physical connections are OK. Can you elaborate?

For Shift Window, how do set multiple wow windows separately? I set up 5 different rules to grab my 5 wow windows, but it only resized my 1st window 5 times (which makes sense - each window is named the exact same thing).

Some Blizz reps have indeed been very clear on that things need to be 1-1-1 (here is an: example). I agree that overall Blizz hasn't been clear nor consistent.

Offense is too strong of a word as I am a fan of all the great ideas and documentation/details people have been giving/sharing (especially you). I do get concerned on approaches which are abusable (like via things like automation or multicasting) because I believe that abuses will help bring more enforcement from Blizz and possibly clarifications or restrictions that we can't live with so I do speak out against those exposures to try to protect the community... We don't know which straw will be the one that breaks the camel's back...

It has been many decades since I studied EE so I apologize if I confused or overemphasized hardware vs electrical connections as that was not my intent... My main point was that I would design the multi-connection keyboard to be where it is not-abusable by design and that would be enforced as the hardware level only allowed each key to be configured to connect to only out USB output at a time. Basically every key on the "FrankenBoard5(TM)" would have the potential to connect to any of the 5 USB clients, but ONLY 1 at a time via something like this Rotary Switch (at least conceptually). Conceptually you could envision a keyboard that looks like something like this on the top but has 5 USB connectors on the side/top and if you flip it over it has 48 little Rotary Switches with "little clockfaces" showing 1-5 on them that you adjust per key with a little screw driver. Conceptually the little switches could look something like this picture for every key (except it would be 1-5 instead of 1-4)... That would give you a very flexible keypad for controlling upto 5 PC/VMs but not supporting multi-casting of any single key to more than 1 target... That would be enforced at the hardware level...

If you had any firmware on the keyboard you could make it all encrypted (like Samsung bootloaders and Knox) and include a Trusted Platform Module (TPM) that WoW clients could check to verify the inputs were from a trusted source...

Regarding ShiftWindow being able to IDing windows separately you need to use a utility/tool like GUIPropView to change the title/name of the window before running ShiftWindow Rule Set. Just launch the 5 windows, append a 1-5 on the end of the window name/title with GUIPropView (or another tool), then run your 5 step ShiftWindo ruleset. Links for the GUIPropView tool and many other utitlies are on the spreadsheet. If you want a very elegant windows management and client launcher you may want to check out the Fuiiboxing tab.

Sorry if the above doesn't make sense. Very busy and in a hurry and working with too much coffee and too little sleep...

[boxblizzard]

Some Blizz reps have indeed been very clear on that things need to be 1-1-1 (here is an: example). I agree that overall Blizz hasn't been clear nor consistent.

Offense is too strong of a word as I am a fan of all the great ideas and documentation/details people have been giving/sharing (especially you). I do get concerned on approaches which are abusable (like via things like automation or multicasting) because I believe that abuses will help bring more enforcement from Blizz and possibly clarifications or restrictions that we can't live with so I do speak out against those exposures to try to protect the community... We don't know which straw will be the one that breaks the camel's back...

It has been many decades since I studied EE so I apologize if I confused or overemphasized hardware vs electrical connections as that was not my intent... My main point was that I would design the multi-connection keyboard to be where it is not-abusable by design and that would be enforced as the hardware level only allowed each key to be configured to connect to only out USB output at a time. Basically every key on the "FrankenBoard5(TM)" would have the potential to connect to any of the 5 USB clients, but ONLY 1 at a time via something like this Rotary Switch (at least conceptually). Conceptually you could envision a keyboard that looks like something like this on the top but has 5 USB connectors on the side/top and if you flip it over it has 48 little Rotary Switches with "little clockfaces" showing 1-5 on them that you adjust per key with a little screw driver. Conceptually the little switches could look something like this picture for every key (except it would be 1-5 instead of 1-4)... That would give you a very flexible keypad for controlling upto 5 PC/VMs but not supporting multi-casting of any single key to more than 1 target... That would be enforced at the hardware level...

If you had any firmware on the keyboard you could make it all encrypted (like Samsung bootloaders and Knox) and include a Trusted Platform Module (TPM) that WoW clients could check to verify the inputs were from a trusted source...

Regarding ShiftWindow being able to IDing windows separately you need to use a utility/tool like GUIPropView to change the title/name of the window before running ShiftWindow Rule Set. Just launch the 5 windows, append a 1-5 on the end of the window name/title with GUIPropView (or another tool), then run your 5 step ShiftWindo ruleset. Links for the GUIPropView tool and many other utitlies are on the spreadsheet. If you want a very elegant windows management and client launcher you may want to check out the Fuiiboxing tab.

Sorry if the above doesn't make sense. Very busy and in a hurry and working with too much coffee and too little sleep...

long as hardware broadcasting is acceptable, we can bounce back. Tab boxing is just awful and no good in fast paced scenarios and even if you can make it work by a thread...it’s not viable long term as it is more work than it has to be.

the truth is, boxing the old days was expensive, I used to 5 box on a desktop back in 2008 and it cost £3000 to have something that was decent enough.

it’s a full circle, we need to use hardware casting gear and budget amd nucs etc

i think all the modern casting software has made boxing so easy and I expensive, it’s been a easy ride for everyone to jump on board.

Time to get our wallets out, and adapt to the policies with hardware.

we will be back in action soon when we all compile a recommended list of hardware for reboot

What I worry the most about is bots, they will grow and become a bigger problem for us as we all
get slammed for being a bot using software, living a life of temp bans.

lets hope blizzard identify genuine boxers and treat us fairly and investigate in person rather than the ban hammer drom
the automated system.