Hi,

Autohotkey
After not being able to find an autohotkey alternative for Ubuntu, I started off using Autohotkey, via Wine. As for the key re-mapping part, it worked Ok. I would have a 20% per hour rate or so to bug autohotkey while playing, which was annoying, but had a bright side in being ripe excuse ammo for losing the last arena match. Unfortunately, although I feel the script I use was very well written (I used this great site's tutorials), I still can't rule out that this may have been the effect of something in the code. However, the script worked great, and without error, in Windows.
Getting to the more important area- multi-boxing with Autohotkey in Ubuntu, this was a big let down. A perfectly working script was now causing the clones to fire their casts with 3 to 6 to infinity and beyond seconds of lag. It was a shame. This was my experience with multiboxing with Autohotkey in Ubuntu using Wine, if anyone happened to have a different experience, I'd be very interested in hearing about it. I miss autohotkey, especially the key remapping part (die hard arrow keys + numpad keybinder, not enough room for all these new spells without one).

Keyclone
I'm not certain where I read it, but eventually I confirmed that keyclone did indeed work with Wine. I eventually decided to give it a try. It seems everything works as it should in Windows, and I can't find anything to be upset about, and I've been pleased with it. So, even though there is really no irony in it in the least, here I am recommending non-free Keyclone for people with linux, and Autohotkey for people with Windows. That's not to say there's anything wrong with Keyclone at all. I'm just really, really cheap.

Alternatives
There are a lot of search results from typing in "autohotkey ubuntu", however, they all seem like work in progress projects that never were quite completed. However, I haven't fished in a while for a linux autohotkey replacement, within roughly 6 months.

Maximizer Program
I do know that Wow Maximizer did not work with Ubuntu unfortunatley. It's been so long since I tried it, however, that I can't be certain. I'm not at my computer at the moment to test whether Keyclone's works in Ubuntu or not. I've used another technique, seen in the my experiences section.

Recommendation
Overall, if you have the time to spare, give autohotkey a try, at least for the sake of experimenting. Perhaps your script / computer will run it fine. Also, check to see if there is any big news in development with a Ubuntu autohotkey/keyclone alternative. If you don't have luck, know that keyclone works fine and dandy.


My experiences with Multiboxing on Ubuntu
Great, great great, to sum it up. I use a very modest, pretty much out of date computer- spec wise (Athlon 3800+ x2 64, 2gb 500something ddr2 ram, geforce 7600gs (with 512ram though)). In Ubuntu, 7 boxing on just that machine is comfortable (some memory is swapped, but fps does not drop under 20.) 5 boxing is swapless, and is 60fps all around. Doing the math, 1 instance of wotlk wow translates to seemingly 310mbs of ram used (on min settings of course). I lust for eventually getting 4 more gigs, and seeing if a 17box on 1 machine will go as well in real life as it would on paper, but gl to me having that many accounts to give it a try.
Using the method described below, ram seems like the only thing stopping me, though I'd imagine the poo quality processor speed / graphic card would need more power eventually. For now, I wonder how many more WoWs I could have open before the fps starts to drop to it being uncomfortable as a result of non-memory space slowdown, as there seems to be a lot of slack.

The individual workspace method
The method that I use is putting one wow instance in an individual workspace. Rather than contend for your graphics card at the same time, this seems to run the other instances at frame rates which allow for casts to not delay to any noticeable level. It also seems to keeps resource use to a seemingly static state per new WoW instance, minus 310mb or so of additional ram required per instance of wow.
As stated before, this equates to 7 boxing with focused windows running at 30-60fps (130 being the record uncapped), and 5 boxing with no memory swapped at 60fps.
Basically, my main problem and reason for settling on this method was because 2 or more WoWs on one screen was overheating my processors, but keeping 1 wow per workspace screen equates to roughly 7 degrees cooler than 2 or more on the same screen.
Adding a SET maxFPS "60" SET maxFPSbk "10" setting to your config.wtf seems to help a bit, to make sure whatever window you have focused gets all the juice. As there was only a mild improvement seemingly from this, it's lead me to wonder if the improvement was just a placebo, and that all wows in their individual workspaces are seen as in the foreground (according to their workspaces). Overall, I feel capping the background wows does help a bit, but not enough for me where I wouldn't second guess it.

It's not without it's flaws, of course. Although spells seem to cast instantly in cloned machines, there seems to be a little bit of lag when the cloned machines are /fol ing you, which results in having to stop occasionally to let them catch up. I'd lay the blame on that happening as a trade off for running each wow in different virtual desktops (workspaces). This presumably as a result rules out competitive pvping via the different workspaces method. But at least it's great for mass leveling, and some of the more layman's instances.

As a final note, I doubt Ubuntu is special about the concept of workspaces. I know macs have them, and I know you could get them on Windows with a theme program like SharpE. However, I don't know if they behave the same way, or whether they would have the same results as an Ubuntu/Linux version of the workspace would via applying the same method.

See ya,

Clue