Keyclone or HotKeyNet?

[nemof]

Hi. I just started dualboxing 2 characters in wow.

With limited experience of 2-3 days I have set up hotkeynet and used the standard wow script that is on the website. It seems to work ok, and the rest is up to me to configure macros etc.

However, ignoring the cost (as thats not a bother to me) would it be simpler to just get keyclone? In other words I am pretty comfortable with HKN, so am I really missing out not having keyclone?

[David]

I`ve been using keyclone at the start when 3boxing but when I moved to 4/5 boxing I went hotkeynet.

The script takes some time to learn but it`s worth. It is a great program in my eyes.

[olipcs]

Well,I'm personaly a big fan of HKN, but as many others I originaly used keyclone, as it was the solution most people recommend for a multiboxing noob..

..and to some points this is true and the realy 'big-feature' of keyclone: it has a graphical gui and for basic multiboxing it is quite quick configured..

..for me, I used keyclone from april 2008 till (I think) september 2008 and then switched to HKN.
This was mostly, because i began to use an FTL-System and wasn't quite happy how keyclone handles the setup of the keymaps (and mostly the hazzle this has, when you try to explain it to others..). So, when Anemo posted the original FTL-HKN-Thread, I looked at the code and imidiatly loved it...
...this maybe, because as someone with some programming experiences grasping the concept of the HKN-Language wasn't that difficult for me, so I tryed HKN and got my complete setup running after one hour :) (the command-reference and sample-scripts helped here a lot!).

Another thing what realy got me to 'never' change back, was, that Freddie was extremly openminded listening to my bramblings of which other features I would like.
And even not all of my suggestions where implemented (special FTL-commands ;) ), there was allways a good dialog about it, and I could allways see, how I as a user could influence the development of new feautures (like <IF Win...>,<If Mouse..>,<SetVar..>,<Templates>,<SetToggle>...).

..don't get me wrong, I absolutliy admire Rob (author of keyclone) for his support of this site, the developement of keyclone and the good support he gives, but what I was missing in keyclone was the lack of new features, to suite my more advanced boxing needs (ftl,virtualbuttons,mouse-overhealing..) and the fix of some bugs (i.e. r/l-modifiers).
So mainly I changed from keyclone to HKN, because I missed some features in keyclone and now I'm loving the freedom HKN gives me to do exactly what I wan't!

So what I would recomend:
Use the solution you like best (or fits your needs best)!
For me all (three) solutions (keyclone, IS, HKN) have their pros and cons and you simply need to evaluate which one suites you best.
..but since you already using HKN without a problem, and HKN has more feature than keyclone, I in your position wouldn't change.
And if you have any question regarding HKN feel free to look in the guide (see Sig.) or simply ask here (or the HKN forum), most HKN users are very friendly and will try to help you (as in all fairness most of keyclone and IS user also would..).

[slash]

I started out using keyclone initially but quickly changed to using hotkeynet.

Personally i found keyclone buggy and restrictive. Hotkeynet is much more powerful but more difficult to set up.

So it comes down to a personal decision, keyclone is good to get up and running quickly. Hotkeynet is more powerful but requires more time initially to setup, there's plenty of info here and on the wiki to help you set it up though.

HotKeyNet is free too!

[nemof]

I think I will stick to HKN. It seems very flexible, the scripting is a more interesting approach and not something that would scare me off.

Quick question.

I want to launch both instances of wow windowed. I know that you'd normally pass the "windowed" argument to them, but I'm not sure how to pass it in HKN.



<Command LaunchAndRename>
<SendPC %1%>
<Run "c:\Program Files\World of Warcraft\WoW.exe">
<RenameTargetWin %2%>


How do you pass command line arugments in HKN?

thanks for all your help so far.

[Kalikiano]

the windowed part I just go into wow settings ingame and click windowed mode then you never have to do that again. Then I do use HKN to resize and remove wow borders.

[keyclone]

hmmm... hotkeynet.com post ('http://www.hotkeynet.com/phpBB3/viewtopic.php?f=3&t=1093&p=7064&hilit=keyclone#p7064')

in the end it depends on what you are looking for. keyclone is pretty simple to set up... technically, just run your wows and start keyclone. done. tweak your do-not-pass and that's about it. want keyclone to auto-start your wows? add that. want keyclone to layout your wows in a cool fashion. add that. simple.

if you want to deal with tweaking scripting code for each key you want to deal with, then hkn might be for you. just be careful (link ('http://hotkeynet.com/wow/wow-rules.html') )

[Freddie]

How do you pass command line arugments in HKN?
I was about to answer, "write the switch after the pathname like this:"



<Run "c:\Program Files\World of Warcraft\WoW.exe" -windowed>

But then I remembered that I changed Run recently without testing it, so I decided to test now before answering your question. It was a good thing because command line arguments didn't work.

I just fixed this and posted a new build, 170, (http://hotkeynet.com/p/download.html) which you'll need for this.

By the way, in case you don't know, there's a reference section (http://hotkeynet.com/ref/run.html) where you can usually find answers to this kind of question.

Thanks for inadvertently reporting the bug. :)