As one of the few HKN users here, I'd never suggest someone use HKN with any intent of "ease of use." Mostly because I'm the one that ends up with pages of troubleshooting newbie scripts, lol. The setup, though it appears to be copy and pasting a script, almost always leads to dozens of complications because the starter scripts are limited and usually require editing to work, which many people are not interested in doing, and doesn't include setups like FTL, built-in assisting, fps capping, core assignments, PiP, window-swapping, leader swapping, window sizing/positioning or even broadcast pausing. It can do a lot of the things ISBoxer can {though certainly not all}, but not without knowing how to code it, and that frustrates a lot of people who just want to run a setup wizard and go.
As MiRai already explained, 1:1 mouse broadcasting is nothing new. All 3 programs you mentioned already have it and have for as long as I've known about them. I'm pretty sure many others that have come and gone also provide it. I'd dare say it's a standard feature in most cases. I switched from Keyclone to HotKeyNet for better mouse broadcasting when Wrath came out. I use my mouse broadcasting hundreds of times a play session and have never had a GM say so much as "Boo!" about it, even when I was being very obvious in very populated areas such as fishing*5 at the OotCS dailiy hub. I don't think I've even seen a post claiming being banned or actioned for 1:1 mouse broadcasting.As a side note: One thing that concerns me about ISboxer (the last thing i am trying to do is bring any ill will to Lax's masterpiece) is the ability to clone mouse clicks across each instance - i may have read into it wrong, but that is a fine line to walk with Blizz's already fuzzy stance at multiboxing (Allowed and by no means discouraged when following ToS rules) - It has not stopped me from using ISB a whole hell of a lot, but I feel slightly safer with KeyClone - Again, I included this at the end because i by no means want to discourage people away from either, the Fuzzy-Logic and Vague conclusions Blizz has left us with is the only reason i included the "issue" in the first place.
What is NOT allowed, is pre-determined or "memory-read" mouse broadcasting. The mouse click must be relative to the individual character. That is if you click the mouse at your master toon's feet, your slave screens can not "rewrite" the position to have the slaves click at the master's feet regardless of where they are. They can only click at the same relative postion on their screen from their point of view. So if you click the dead center of the master's screen, your slaves should all be clicking dead center of their screen. You can not click the center of the master's screen and have that send the mouse cursor on the slave screens to a different location based on coordinates or pixel-reading.
There's very little that's actually "fuzzy" at this point. If it is, people will argue it here until a consensus is reached - usually in the form of a Blue post on the official forums/tweets when someone raises the question there or via a GM response from petitions in game.
Psssh, Jamba deals with dialogues for me.
But, mouse broadcasting is always useful for portals, tables, fishing, gathering, command boards, those stupid cauldrons in ZG etc. Like most things in multiboxing, it's not required, but it sure makes life easier.![]()
Connect With Us