This is something I have been pondering over the last few days too. I then began to wonder if use of the CAPS LOCK key may, in fact, violate the one keypress one action rule because the operating system effectively generates a SHIFT-A for a press of A. Start thinking like this and you open a whole new can of worms with arrow keys, PG UP and the numeric keypad.

Now, obviously, I am just being silly with the extended keyboard functions and this does not strictly relate to the example of generating a different modifier for each session. I'm still trying to decide which way Blizzard would go on this one as it is, ultimately, entirely down thier discretion. Modified or not we are effectively sending one "key" with the modifier "held down" on the other sessions as defined by the hotstrings. Even a "white" or "black" list can potentially be a problem as it allows key "A" to pass but not key "B" resulting in a differing result across sessions depending on which has focus.

To take the concern to it's logical conclusion ANY use of hotstrings could potentially be a problem as it allows different keys to be pressed on multiple sessions for a single hardware event even though only "one key" is pressed on each WoW instance. The answer is uncertain, but is dependant on how Blizzard view our installations. Do they look at each instance of WoW in isolation or as a group of sessions? The only people who can answer this question will not, unless at some future time they decide we may not continue.

I [s]would suggest[/s] (EDIT: I wouldn't dare to advise anyone on this matter) have decided not to worry about it too much until Warden issues a warning about keyclone, we can be almost certain that Blizzard knows precisely what the keysender is capable of.