Well after the last patch I somehow lost my hot key for a CH loop. I rarely need it but of course since I lost it I was called into a loop. Franticly looking for my hot key with no luck I had to create one asap. Well for some reason the one I created doesn't look quite right to me, or I guess it doesn't seem to look like what I remember. There was at least one thread here about this and I think if I could find if (I did try) I'd remember what I had. The search function doesn't bring up anything - at least with what I tried.

So if any can find that (those) threads that would be great. Or post what you use. I'm sure I'll remember what I used to have after I see the options.

I know i was using 2 casts for fizzle. I was using all 5 lines.

Line 1 >/cast 7
Line 2 >/pause 3
Line 3 >/cast 7
Line 4 >/pause 12
Line 5 >/1 (6) CH INC TO (%T) cast now>> NEXT PERSON<<

we dont use CH rots anymore but here goes:

/cast 1
/5 (#) ICH inc to < %T > - Next Person (#)
/g doing CH Rotation on < %T >
/cast 1

I'm glad my guild never makes druids do this ****.

Druid CHs are the pwn!

My hotkey is kinda like

/shou # CH inc < %T > xxxxx Next!
/Cast 4

If needed i add a small pause like

/Pause 5 or 10

Nothing special

I do it same as my Chlorobon key

/cast 5
/cast 5
/cast 5
/cast 5
/g Droppin the Chlorobomb on -----> %t

Change one of the cast lines to a pause if needed

since sit/stand is not relevant anymore as you auto-stand when casting, button can be:

/cast 8
/2 dru CH inc to %T , next in line - Vekx
/cast 8
/pause 30
/2 next in line --- VEKX cast NOW

or if its going to be a long fight and you really need to med between casts:

/cast 8
/2 dru CH inc to %T , next in line - Vekx
/pause 30, cast 8
/2 next in line --- VEKX cast NOW
/sit

you can add the name of the person after next one, in case next dies, goes oom or is under attack and cant cast, like:

/cast 8
/2 dru CH inc to %T , next in line - Vekx (Sildan)
/cast 8
/pause 30
/2 next in line --- VEKX (Sildan) cast NOW

if your MH prefers counting and one-line chain key as more flexible (i personally dont like counting), then:

/cast 8
/2 dru CH inc to %T , next is Vekx in ***3***secs
/cast 8
/cast 8

Insanely long (multiline) CH messages with names and next names and pauses and whatnot..
What we have:

/cast 7
/gu CH === %t === #
/pause 4, /cast 7
/pause 4, /cast 7
/pause 4, /cast 7

Chain goes by the number in CH message. It's much easier to say 'skip 3' than it is to re-write the message and remember who's where. Chain goes to /gu, fast heals into /rsay, that's it.

Very similar to Wine's key except I don't use pauses (think we actually lose 1 cast chance without a pause, but I don't like pause in a heal button).

/cast 2
/ooc ( 1 ) %T ( 1 )
/cast 2
/cast 2
/cast 2

We keep our OOC short and sweet. All we need to know is who is being healed %T and what # you are in rot.

Last time we used druids in a CH rot was in PoTime when having up to 9+ people in CH rot was very helpful in keeping a MT alive. We use OOC for main rot, Shout if we have a rampage or a second rot (a la tormentors).

Etana's keys make my head hurt hehe. That's how my first guild I joined did CH rots, but it's really not effective once you get up against PoP named and higher.

Ours is pretty simple.

/cast 7
/4 Incoming heal ( %t ) - ( next ) next
/cast 7

Thanks all. I think I can get what I like out of all these. But one more question.

If you /cast 8 first.... don't you have to wait for the 10 sec heal to finish before the line-2 message displays?

I liked this below but I remember sending the 1st message before the first cast:

/cast 8
/2 dru CH inc to %T , next in line - Vekx
/cast 8
/pause 30
/2 next in line --- VEKX cast NOW

So I'm thinking:

/cast 8
/3 # CH inc to %T
/cast 8
/pause 60
/3 # (NEXT-NAME) cast NOW

Or:

/3 # CH inc to %T
/cast 8, pause 3
/cast 8
/pause 60
/3 # (NEXT-NAME) cast NOW

If you /cast 8 first.... don't you have to wait for the 10 sec heal to finish before the line-2 message displays?



Nope, it sends all commands through unless you put in /pause.

/3 # CH inc to %T
/cast 8, pause 3
/cast 8
/pause 60
/3 # (NEXT-NAME) cast NOW

I think you can have two commands only when you use /pause first, followed by anything else. Every othere combination of more than one command per line wouldn't work. I'm not sure about that, I just have a feeling that I've read about it somewhere :)

BTW, can I have hotkeys use hotkeys or something like that? Can I beg / forage maximum 5 times with a single key or is there a trick to get more without using outside programs?

I think you can have two commands only when you use /pause first, followed by anything else. Every othere combination of more than one command per line wouldn't work. I'm not sure about that, I just have a feeling that I've read about it somewhere

This is correct. They only allow two commands per line when one of those commands is a /pause.

I believe the thought process behind this would be to prevent folks from using hotkeys to create macros like /fish ( actually doabilitiy yada yada yada ), /autoinventory, /pause, /fish, /auto/ pause, /fish, /auto, /pause, etc....

You can currently create a macro but only a 5 step one, thus not allowing you to walk away for any period of time.

Like i said Druid ch rots are the pwn :biggrin:

http://www.ajjantis.de/druidsown.JPG

Ewwww.... thank god we don't do druid rots... anymore... since elemental planes lol

druidrots4tw!

I've never heard of the /pause command before, so please excuse my newbness. If the hotbutton said /pause 30, how long does the pause last before executing the following command? Thanks in advance

I believe /pause 30 is three RL seconds...I'm sure someone here knows for certain.

Winenose and Kaidman - you are right, simple keys with one line message and numbers instead of names are best for raiding guilds. however, i got the impression that Vekx is not so used to chains, which means that either does not raid very often, or just as a druid is not called for chain often. from personal experience, for chrota in raids of casual guilds or raid alliances it is best to have two lines and state explicitly who has to heal and when. this is necessary because you often have unexperienced people healing or even druids only rotation!

Vekx - it doesnt really matter which line comes first - message or cast. the difference is that the second command will come with some miliseconds delay. So both:
/cast 8
/3 # CH inc to %T
/cast 8
/pause 60
/3 # (NEXT-NAME) cast NOW

and

/3 # CH inc to %T
/cast 8
/cast 8
/pause 60
/3 # (NEXT-NAME) cast NOW

would work great. but keep two lines of /cast #, in case it frizzles. and make a second key with one line only if you happen to have a MH from a raiding guild.

Vekx - it doesnt really matter which line comes first - message or cast.

While I agree with this statement, I think it important to add to it.
I will say, it doesnt really matter whether the message line or cast comes first, however, it is imporant that everyone in the chain do it the same way or you have an inconsistant rotation.

from personal experience, for chrota in raids of casual guilds or raid alliances it is best to have two lines and state explicitly who has to heal and when.
My personal experience is exactly the opposite. Saying who to cast next and when slows down the healing, so you have to account for that. (If you delay 3 seconds and then say "heal now" then you have nearly a half second delay of network latency and human reaction time.) It also creates a LOT more spam in the heal channel, which is a bad thing. Especially if someone heals late/early/gets of out order, with a single message it is reasonably straightforward to fix, but with delayed messages text starts flying everywhere and it's a real mess.

One thing that I do think does make a big deal, especially in fights where healers may need to be replaced because of low mana or death, is to put a number at the beginning. My heal hotkey looks like this

/2 (3) druid CH to %t, KIRYA next in 2
/cast 4
/cast 4
/cast 4

With the number there (in that example I'd be the 3rd person in the chain), you can easily replace a healer by putting someone else in at the number. After my guild used that method for a while, I didn't even really look at the names very much, just followed the numbers. It was very, very easy, by far the best system I've used.

To the person that asked, /pause 30 is indeed supposed to be 3 RL seconds. I wouldn't set my watch by it, but it's reasonably close.