Strange round-robin behaviour

My understanding is that the round-robin option should send keystrokes to each character slot one after the other (in some fixed order). However, in my case, the option appears to be skipping keystrokes--or maybe ignoring is a better word.

I loaded up the debug console to see what buttons my characters were receiving and I noticed that a simple, single-step keystroke action set to round-robin to 'all' would only send a keystroke to one of my characters on every other keypress. When I added a Do Mapped Key Action (assist in this case) before the Keystroke Action to make things more interesting, I got even stranger behaviour: I had to alternate between 1 and 3 presses of the keyboard before one of my windows would receive the keystroke I expected it to get. Any actions set to broadcast to all within the same mapped key worked as intended, by the way.

This isn't a big issue if I'm just spamming the ability in question because sooner or later I'll get to every character, but it's complicating some of my less spam-friendly mapped keys. I could always split things up into separate steps, but I'm wondering if this is a bug or if my assumption of how the round-robin option is supposed to work is flawed.

P.S. If it makes any difference, I'm experiencing the issue in SWTOR using a team of 4 characters split evenly across 2 PCs. (Could the round-robin option not be playing nice with a multi-computer setup?)

[MiRai]

Share your profile.

[lax]

(Could the round-robin option not be playing nice with a multi-computer setup?)

No. However, if extra processes are loaded they would be affected by "all". SWTOR purposefully uses multiple processes per game instance, so it may be including the extra ones. You could use an Action Target Group with your Characters specifically added, or you could probably also manually type (or paste) in the Target box "isboxer" (with no quotes). There is an Action Target Group called "isboxer" automatically which includes all of your Characters.

Oh, that's sneaky. Setting the target of the round-robin action to any group other than 'all' did, indeed, fix my problem. I'll have to keep an eye out for that elsewhere. Thanks for the tip!