Hooks work like this. The last application to install the hook, the first in the chain it goes. The first app in the hook may prevent latter ones from getting events. So if you run keyclone after kavoom, and kavoom is on a client PC, the chances are, keyclone would send keys to the client as well. This is the reason Octopus has the "detect keyclone" option and attempts to jump in front of it. So I'm suprised that doesn't work, (it defaults on If i remember correctly). Theres a variety options to programmers of course, but otherwise you could run kavoom after keyclone and hope Kavoom is coded to cut off the hook chain on clients. That also assumes keyclone is not reinstalling its hooks during runtime, or doing anything to trigger hooks on kavoom clients (if applicable), and so forth. See all the scope of possibility... :wacko: