[Discuss] Mouse vs Click Broadcasting

[olipcs]

For me it would be ok, as it still relates to the paradigm:
"one (ingame) action per (mouse-)keypress"

[Vyndree]

For me it would be ok, as it still relates to the paradigm:
"one action per keypress"

But does that mean you define mouse movement on an x,y axis to not be an action?

There's still the action of a keypress (that precedes all GCD arguments). With keyboards, it's simple -- there is no x,y axis. Only a Z axis. But mice have 3 axis -- x,y (movement) and z (keypresses). Are you saying you don't consider the x,y (movement) axis necessary, and as long as it's done on one PC/client/screen it can be "automated" on the others? (I use the word "automate" while kicking myself for not being able to think of any other word that seems to fit)

[TheBigBB]

So let me get this straight. It's possible to click somewhere and have that click broadcasted to the same coordinates on another client?

[Crucial]

As long as there is no dynamic decision making about where to click based on events in the game then the only difference I can see between mouse broadcasting to multiple computers currently is that the coordinates and button pressed are fixed rather than originating from the pointing device itself. You still have to click or press something to make it happen and there is no automation right?

[Vyndree]

So let me get this straight. It's possible to click somewhere and have that click broadcasted to the same coordinates on another client?

Anything is POSSIBLE. Whether or not it should be/shouldn't be allowed by the rules is up to Blizzard, I'm just curious what other peoples' thoughts are given the precedent allowing it would set.

[olipcs]

So let me get this straight. It's possible to click somewhere and have that click broadcasted to the same coordinates on another client?

Yes! (For example use HotKeyNet)

As long as there is no dynamic decision making about where to click based on events in the game then the only difference I can see between mouse broadcasting to multiple computers currently is that the coordinates and button pressed are fixed rather than originating from the pointing device itself. You still have to click or press something to make it happen and there is no automation right?

I second that! As long as there is not a dynamic decision making, I also would consider it ok, but hey, the final decision will make blizzard...
...and for me every outcome would be ok, as mouse-briadcasting is handy, but i use it not very often...

[TheBigBB]

So let me get this straight. It's possible to click somewhere and have that click broadcasted to the same coordinates on another client?

Anything is POSSIBLE. Whether or not it should be/shouldn't be allowed by the rules is up to Blizzard, I'm just curious what other peoples' thoughts are given the precedent allowing it would set.

I am just trying to understand the question perfectly.

Most of the time, mouse positioning on the screen has no in-game functionality, and it serves basically no purpose unless you're actually clicking. There are only a couple of things you can do with mouse broadcasting + click that you normally couldn't: targeted AOE and menu selection. Menu selection seems like a non-issue since it's not affecting gameplay. Targeted AOE works that way because it targets a ground location which can't be specified any other way. However, if you moved your mouse there and clicked on one client and the mouse was broadcasting, I don't see any practical difference from keyboard multicasting. You still targeted something and clicked a button. The automated X.Y movements would just be replicating the movement you made.

[olipcs]

... and as long as it's done on one PC/client/screen it can be "automated" on the others?

..mainly, yes, this what my instincts say, even if it may be controversy.

btw. you mentioned the minimap-ping-controversay, my opinion on this is:
- blizzard did fix the minimap-pinging-thing, yes
- but: they never said (to my knowledge) that they don't want multiboxer to be able to do something like casting targetet-AoEs, if they specifical say that, i'll stop using it imediate.
- what they simple did, is making the ping-minimap.. not an option to cast such AoEs, but they never said, they changed it because of multiboxing, and we are not allowed to use another approach, or am I wrong?

But to be honest, the answer of blizz will clarify it, and as good multiboxers we will act approriate...

[Schwarz]

Can someone clarify what dynamic decision making is.

[elsegundo]

my opinion is that this is fine. there is no automation. with mouse movements in sync, a lot of things would be easier. i am not talking about mapping mouse clicks to action bar buttons because i think those things are easier to do with hotkeys+keyboard broadcasting anyway. but things like changing camera angles (not just turning), placing AoE spells, whether it be healing spells or damage spells, and on-mouse-over commands. actually for on-mouse-overs, i think that having all the slaves "see" the main's mouse pointer would be a much better idea. but then again, this might give multiboxers too much of an advantage. but for the most part, i would love mouse movement broadcasting only for the camera movements. in any case, mouse broadcasting should not be forbidden. the minimap ping function has little to do with this, as it doesnt use mouse broadcasts to perform blizzards, rain of fires, or circle of healings. instead, it ignores where the mouse pointer may be and sets the target of the AoE spell at the location of the main.