Macros for spells/abilities - Page 3

Swishy · 07-16-2008, 11:23 PM

Quote:

Originally Posted by Dants

That's always been bugged. I tried to do the same thing as you before, and it all worked but it sent a tell to the wrong person. Mine was something like:

/target_group_member 0
/useability Jester's Cap
/tell %T JC on
/target_previous

You'd have to hit the macro 2x for it to send a tell to the correct person.

I created a .txt file with just that last night and used it using the /do_file_commands command in game to link it to a button. It did of course fail (as I mentioned in the other thread), so I'll give your 'double tap' a shot.

Thank you for the feedback Dants

Melodias · 07-18-2008, 10:21 AM

Quote:

Originally Posted by Bewts

I jcap the 3 MT healers and myself on PotM casts, bout it. But then again we run 2 troubs so uh my counterpart gets to prioritize the dps. Normally its wizards and asses from what I can tell. She also cast's PotM first so MT healers don't have to wait on a Jcap.

In case you were wondering my macro is off of Fetish UI. I just have 5 hotkeys setup with Jcap. First one goes:

/useabilityonrt Jester's Cap
/tell %rt <insert leet message>
/raidsay <insert leet message> on %rt

All the DPS classes are told to have a macro that sends me a tell -- first come first served. Long as were killing shit fast I don't care who gets jcap to include healers when they want to distract themselves.

The next 3 Jcaps I just put the name of a MT healer in the first 3 with no tells they have it. No point in spamming them more than they need. Typically Defiler gets Jcap first followed by Templar (depends on pull TBH and your point of view on RoA vs Jcap) and then warden is the last.

The final jcap macro is the same as the ones above but for myself. This macro is right next to my PotM macro to limit movement of my mouse when I PotM/Jcap myself. All these macros are right above my dps CA/Spell bar(s) so I can limit mousemovemnt while dpsing. I still end up all over the place but a 4 inch long window by a 2 inch high window for mouse movement is a lot better than a 8 x 6 window.

Also, fuck the XML macros from the raid windows. You spend waaaaay too much time moving your mouse around to DPS effectively. Not to mention people aren't always in the same spot in the raid window due to LD's or moving members around or not having the same 24 people every night so your muscle memory gets fucked up soon as the raid setup changes.

Go into your fights with a plan on who's getting Jcaps and when. I think you can at most keep a rotation of 5 Jcaps before the first person's timer is off and is eligible for it again. If you are going further than 5 deep worth of people who OMFG I NEED JCAP TO PARSE then get another Troub.

If you have a mythical Dirge, you might want to consider adding them in a Jcap rotation to boost the DPS raidwide compared to someone Epeening over their 7k - 10k Parses - just some food for thought as I haven't really looked into it but wondered if it would be a more effective contribution to raidwide DPS. Kinda depends if you are mage heavy or melee heavy.

It'd be a tough call for us considering at any given time we have 2 wizards 2 Illy 2-3 Coe 1 Necro 2 Crusaders 2 Troubs. Thats a lot of casting going on for us and a lot less auto attacks when half the raid not counting priests are pure casters / hybrid casters.

As Pinkell's (Bewts) counterpart, we have our macros down to a science. I PotM first (we both have raidwide PotM) and he JCaps the MT healers first. My 3 JCap macros are set to the 3 that display the highest DPS for our raid group in that specific order. It just so happens that the order is Wizard, Brig, Assassin. On the longer fights, after we both go through our rotation of 3, we both have a JCap macro that hits the last person who sent us a tell. We trust our guildmates not to abuse the request and to know when a JCap will benefit themselves the most for the benefit of the raid as a whole and it generally works really well (there are always rare exceptions, but he and I know when to skip it). With 2 troubys running each raid ..... there is constant PotM running and back to back JCaps. The trick there though .... 2 troubys who get on well with each other and can work well together. Pinkell (Bewts) is just amazing and together he and I make the Troubador class look GOOD!!

We don't normally run with a conjy, ..... but when our guild conjy does sneaks his way into the raid ....any self respecting troubador never JCaps a pet!! That's just .....ewwwwww

Taius · 07-18-2008, 11:06 AM

@Melodias

I like the idea of a /tell - cap return thing. I havent found a need to use it yet tho.

Your assassin could do with a firework lit underneath him if he is getting outparsed by a wizzy or brigand btw.

Whats the reasoning behind a wizzy getting capped before the brig? AFAIK the brigands dispatch makes the biggest overall difference to a raid parse, so why arent you capping the brig as a matter of priority?

Melodias · 07-18-2008, 01:41 PM

Well Taius ... I suppose I misrepresented my JCap order. The wizard and assassin are both in constant competition for that top spot on the parse, it's always one or the other. I JCap the wizard first because it just seems more appropriate for a trouby (that and the fact that he's the guild leader, heh). Then I get the brig for obvious reasons. We run 2 brigs on our raid setup so I'm okay getting him second ... they have their dispatch rotation worked out well.

The theory behind the /tell JCap macro is to let your raid members know they have to create their own macros to send the tell to you requesting it. And, you're trusting them to know the difference between teamwork and being a parse hog.

One major down side to the /tell JCap macro....
I wear my anon tag, so occasionally a friend not on raid will send me a tell asking me something or other and it will sneak in between my request /tell and my hitting the macro button. The result is that friend gets a response tell saying "you've been JCapped" and I announce in raid chat to my whole guild that some random person sitting in QH just got my JCap. At that point ....all red in the face I have to switch targets to cap the person I was supposed to cap which defeats the whole point of a macro. I guess nothing is perfect.

Bewts · 07-18-2008, 11:20 PM

Both the Assassin and Wiz consistently parse 8-10 on VP trash, its pretty irrelevant who gets it first long as they get it to keep their big hitters hitting with the JCap on them.

[[[ THAT IS THE WHOLE REASON FOR THE /RT MACRO ]]]

By utilizing the /RT macro you successfully allow the players to ensure their long recast skills are shortened and are used more often and it puts the buck on them to ask for it when needed instead of leaving it to the Troub's to guess which is incredibily INEFFICIENT!

[[[ THERE IS NO POINT IN JCAPPING SOMEONE WHEN THEIR DPS SKILLS ARE DOWN ]]]

As far as brigands getting dispatch as a priority, with 2 of them on the raid basicially we have dispatch on the mob every chance we can get as is. We might be able to sneak in an extra dispatch on a mob but we haven't found our dps on the raid... lacking in the slightest. If we did, we may consider getting brigands dispatch more as a priority but unless our DPS starts to suck consistently there is no point.

Not to mention if your DPS is sucking due to lack of dispatch there is a bigger fucking problem with your DPS classes than getting the brigand's dispatch off more often.

Ballads · 07-19-2008, 11:19 AM

Quote:

Originally Posted by Bewts

Both the Assassin and Wiz consistently parse 8-10 on VP trash, its pretty irrelevant who gets it first long as they get it to keep their big hitters hitting with the JCap on them.

[[[ THAT IS THE WHOLE REASON FOR THE /RT MACRO ]]]

By utilizing the /RT macro you successfully allow the players to ensure their long recast skills are shortened and are used more often and it puts the buck on them to ask for it when needed instead of leaving it to the Troub's to guess which is incredibily INEFFICIENT!

[[[ THERE IS NO POINT IN JCAPPING SOMEONE WHEN THEIR DPS SKILLS ARE DOWN ]]]

As far as brigands getting dispatch as a priority, with 2 of them on the raid basicially we have dispatch on the mob every chance we can get as is. We might be able to sneak in an extra dispatch on a mob but we haven't found our dps on the raid... lacking in the slightest. If we did, we may consider getting brigands dispatch more as a priority but unless our DPS starts to suck consistently there is no point.

Not to mention if your DPS is sucking due to lack of dispatch there is a bigger fucking problem with your DPS classes than getting the brigand's dispatch off more often.

There is a point in wizards at least. Just because fission and mb is down they still can get a lot out of jc. Any good wizard will have a different cast order with JC to take full advantage of it. Not to mention if they know they will get JC every 2 minutes, they can adjust their use of big skills to fit on that time table. Most people will always want JC on pull. When doing trash 30 second encounters with 10 seconds between each pull (ie vp trash) I like to narrow my JC down to 3 people. Myself, wizard, and assassin. I have an act timer that tells me the persons name when their immunity is down. When it says the name i look at the mobs hp, over 50% cast right then, under and i wait till next encounter. The only exception being myself who i wait and use it every other potm. The most inefficient use of JC to me is to have it up and not cast it. Which is what the "tell me when you want it" method led to a lot of. Custom triggers in act are your friend. If you can't figure out how to set it up ill make a post of how to do it.

Taius · 07-19-2008, 05:33 PM

Fair point. I think we are running with 1 brig usually, so I cap him first.

Bewts · 07-19-2008, 07:06 PM

Quote:

Originally Posted by Ballads

There is a point in wizards at least. Just because fission and mb is down they still can get a lot out of jc. Any good wizard will have a different cast order with JC to take full advantage of it. Not to mention if they know they will get JC every 2 minutes, they can adjust their use of big skills to fit on that time table. Most people will always want JC on pull. When doing trash 30 second encounters with 10 seconds between each pull (ie vp trash) I like to narrow my JC down to 3 people. Myself, wizard, and assassin. I have an act timer that tells me the persons name when their immunity is down. When it says the name i look at the mobs hp, over 50% cast right then, under and i wait till next encounter. The only exception being myself who i wait and use it every other potm. The most inefficient use of JC to me is to have it up and not cast it. Which is what the "tell me when you want it" method led to a lot of. Custom triggers in act are your friend. If you can't figure out how to set it up ill make a post of how to do it.

My raid members know to spam me with Jcap requests on trash and know on named they probably won't get one with me JCapping the MT healers. Whenever the Jcap isn't being request I typically toss it on a MT healer just because thats who's on my 3 macros. Rarely it's up more than a few seconds during a fight before someone gets it.

I fully agree that not using it unless requested is just as inefficient as using it on someone when their skills are down. The system Melodias and I have combined pretty much ensures we have Jcaps flowing to as many people as possible either utilizing the /rt system or our specific people to macro.

As I said earlier, its all about having a plan before hand and then executing it while you dps. Outs works well for us it seems except when I forget who's turn it was to PotM and we cross our PotMs!

Swishy · 07-20-2008, 07:49 PM

As posted in the 'automated cure' post in the general forums, I finally got my working. For those interested the 'command' lines are as follows:

/target_group_member x
/useability Jester's Cap
/telltarget You have Jesters <----- note that this was the bit that didn't work. /telltarget instead of /tell %t has fixed it.
/target_previous

So there you have it. Of course not everyone will want to know this, but I do think it's useful for those whom don't have profit or the windows are too small etc. Of course this can be adapted to suit any other class as they require.

Thank you to those whom replied to my questions - your ideas and prompting is greatly appreciated

Dants · 07-21-2008, 02:57 PM

Quote:

Originally Posted by Ballads

There is a point in wizards at least. Just because fission and mb is down they still can get a lot out of jc. Any good wizard will have a different cast order with JC to take full advantage of it. Not to mention if they know they will get JC every 2 minutes, they can adjust their use of big skills to fit on that time table. Most people will always want JC on pull. When doing trash 30 second encounters with 10 seconds between each pull (ie vp trash) I like to narrow my JC down to 3 people. Myself, wizard, and assassin. I have an act timer that tells me the persons name when their immunity is down. When it says the name i look at the mobs hp, over 50% cast right then, under and i wait till next encounter. The only exception being myself who i wait and use it every other potm. The most inefficient use of JC to me is to have it up and not cast it. Which is what the "tell me when you want it" method led to a lot of.

Pretty much the exact same way I do things.

Quote:

Originally Posted by Swishy

As posted in the 'automated cure' post in the general forums, I finally got my working. For those interested the 'command' lines are as follows:

/target_group_member x
/useability Jester's Cap
/telltarget You have Jesters <----- note that this was the bit that didn't work. /telltarget instead of /tell %t has fixed it.
/target_previous

So there you have it. Of course not everyone will want to know this, but I do think it's useful for those whom don't have profit or the windows are too small etc. Of course this can be adapted to suit any other class as they require.

Thank you to those whom replied to my questions - your ideas and prompting is greatly appreciated

Thanks for the info. I'd make a new hotbar that I could switch to when I group with these macros, but I'm all out of hotbars!!!