Differences to CloneKeys for Users

Supports low level macros (keypresses on the front window can cause several keypresses on the others)
Is ready for network distributed MultiBoxOSX setups

Internal Differences to CloneKeys

Lower Level (it works with event taps, not Carbon events)
Uses Cocoa/Objective-C for GUI and even callbacks, therefore there is less (visible) code in the project (I admit I'm not a Carbon guy and the amount of code needed always scares me).

Similarities to CloneKeys

I'm using the same method for fixing that Leopard 10.5.6 problem, thanks to the authors.
I haven't quite reached my goal of somewhat cleaner code. While there is much fewer code (due to Cocoa/Objective-C) it looks very ugly :(

Important! Everything is hardcoded at the moment, I haven't had the time for a decent UI. So at this stage it's just a working prototype. Download only if you are an experienced coder.

Genesis

When after a WoW hiatus of several months CloneKeys stopped working due to Mac OS X 10.5.6 it first came into my mind to build my own. I then realized that it was still working, just not at the login prompt anymore. So I continued using it.

After some time I figured I'd like to dualbox a melee attacker (Paladin) with a ranged attacker (Hunter). So far I had only dualboxed with symmetric chars, and mostly ranged. Now I had the (usual) problem that my second char had to break autofollow on attack, which is very inconvenient with CloneKeys because you have to press an additional key. So I built my own version and implemented a very crude low-level macro support, that is, keypresses can cause several keypresses in the other window.