Printable View
well, i guess it shows how much we all enjoy multiboxing... the mere hint of anything and we jump.
i guess i was being a bit over protective and sensitive.
i sincerely apologize to Narcoz... one of our newest members.
i'm usually not that jumpy and that's not how we want things to be around here.
No offence taken at all, don't worry about it Keyclone. I work as a developer myself so i know we can fall in love with the apps we write. However I didn't mean to attack Keyclone(the app), but merely question the Round Robin function. (which we also finished discussing) :)
And my script is (as I said before) no substitute or competitor for keyclone. It's a crude hack for tech savvy people. The TCP server for instance accepts only 1 client connection, and to fix that one would have to build (i imagine) yet another layer of hacks to spawn threads for multiple clients (when threads are not, as far as i know, directly supported within AHK, but side-effects of key-presses, so you can just imagine what mess that would be).
You have a product, documentation and support. <- That is worth paying for.
And I might yet become a customer if I get tired of the AHK tinkering.
Finally I want to thank you for your "logo" that you use as signature. The picture with the 5 mages casting Firebolt. That picture was what made me decide to buy three more accounts and start boxing a full group. (I've been lurking here for a few weeks) ^^
I have a somewhat loosely related question. My first having been answered (can I create a round robin with a macro), the second is what sort of reset should I use?
I'll be a bit more specific now, I'm planning to start two mages so I can multi-box two toons from scratch (I actually created them yesterday - on the same account :huh: shows how much I still need to think about it, lol). I wanted a macro to cast FN on the main toon and then a second FN on the second key press on the second toon. But I was wondering about an optimal reset value.
Obviously the cooldown of FN seems sensible, but the reset is from the last time you use the key, so what happens if I use my first FN and then don't need the second one for 10 secs. The macro won't reset by the time the first FN is off cooldown.
Do you think I'd be better doing a shorter reset in the hope that I need to use both or something like the following:
/castsequence reset=24 Frost Nova, , Frost Nova
/castsequence reset=24 , Frost Nova,
I can't quite tell if that would help or just make it more complicated. Yes I could just try it out I guess and learn from that, but it will be the weekend before I get any levelling time on them (when I remember to remake one on my other account...) and I'm a bit bored, so enjoying planning my little toons.
Edit: Just read that it resets to the start automatically when it runs out, so reset=24 would work fine
One thing to note here is that round robin can be used to replace /castsequence macros. You do not set a delay on round robin. You control the delay of a round robin by using your finger :PQuote:
Originally Posted by 'Kel',index.php?page=Thread&postID=38602#post38602
If you are going to use a /castsequence, then there are a couple of things to keep in mind. Round robin is superior for some scenarios than the traditional /castsequence.
For example, if you have 4 shaman and you want to use a heal rotation you might have a series of macros like the following:
Shaman1 /castsequence reset=10 Healing Wave, , ,
Shaman2 /castsequence reset=10 , Healing Wave, ,
Shaman3 /castsequence reset=10 , , Healing Wave, ,
Shaman4 /castsequence reset=10 , , , Healing Wave
I used what you might think would be a good reset here of 10 due to the total cast time with talents for Healing Wave being 4 x 2.5 seconds each. This would be great if you never wanted to have more than one shaman casting Healing Wave via this button at a time. Here is how it works. On the first press of the button, shaman1 starts casting for approximately 2.5 seconds, on the second press of the button, shaman2 starts casting and so on. However, if you press the button more than once in 2.5 seconds, any shaman that is currently casting Healing Wave will ignore the button press. This will get your /castsequence out of synchronization. For it to work correctly, you have to wait for the first shaman to finish casting before you press the button again. In situations where you want to have more than one heal on the way, then this type of /castsequence needs a much shorter reset value. You would probably need to set it short enough to allow you to get however many Healing Waves off that you would ever want and then reset. So if you wanted to be able to have 3 Healing Waves in progress at the same time, you might think about a 7 sec reset or maybe even shorter.
Now as I said, round robin doesn't care about this. To accomplish about the same thing using round robin, you would just create your Healing Wave macro and drop the macro on the same button on each shaman. Then in Keyclone, you would add that button to the round robin list. The Healing Wave macro would not have a /castsequence in it. It would be a /cast [target=focustargettarget] Healing Wave or whatever you prefer for your normal healing macro.
On the first press of the button, Shaman1 would cast Healing Wave, on the second press, Shaman2 would start casting and so on. If you wanted to get three Healing Waves going at the same time, then you would just bam bam bam hit the key three times. On the next press of the key, Shaman4 would cast Healing Wave. On the 5th press of the button, you would be back to Shaman1. This is different than how a /castsequence macro works. If you pressed the heal button 4 times in rapid succession to get 4 Healing Waves going at the same time, the 5th press, no one would cast. This is because Shaman1 ignored keypress 2, 3, and 4 because he was casting; Shaman2 ignored keypress 3 an 4; Shaman3 ignored keypress 4; Shaman4 is still in sync with his /castsequence. On the 5th keypress though, Shaman1 thinks its really only the 2nd keypress, Shaman3 thinks its the 3rd keypress, Shaman4 thinks its the 5th keypress, but it is not his turn to cast again until the 8th keypress.
To me, round robin is far superior for this kind of situation. For instant cast spells, either solution will work and will give pretty much identical results to the other. But for spells with a cast time, you have to be aware of how a /castsequence works to get the results you're looking for. Using a shorter delay may give you the results you're looking for.