Suggestion (plea!) for an additional macro option for Jester's Cap

[verydanger]

Hi! I love playing a troubador, but there is one thing that sometimes makes me want to play a different class alltogether.And that is them pesky J-cap macros. Having about 8 different macro buttons for it (with new target's every night), keeping track of who is immune when, etc.What I'd like to do is run a single macro with 4 or 5 names, and simply press it whenever it lights up - then someone on that list gets it. No need to keep track of who is immune or who is out of range - just click and continue fighting. The problem with this is though that people of course want to KNOW when they get j-cap, so I need to send them a text macro. Which makes this handy single macro useless, since it doesnt allow you to send a tell to whoever got the J-cap. So I have to go back to using 8 macros, editing them every night, and using ACT to keep track of immunities. It's doing my head in sometimes.So my plea is - please allow Jester's Cap to be macroed with both a target name AND a /tell to the target. Whoever the J-cap landed on would get the /tell. Something like this:MACRO:ROW 1: Ability: Jester's Cap. Target: Name #1. Message: "You have JC!"ROW 2: Ability: Jester's Cap. Target: Name #2. Message: "You have JC!"ROW 3: Ability: Jester's Cap. Target: Name #3. Message: "You have JC!"ROW 4: Ability: Jester's Cap. Target: Name #4. Message: "You have JC!"Thank you for reading my suggestion, I hope it made sense for more than just me.

[Inggy]

<p>Not to shoot a hole in your idea but .... </p><p>If your macro works as intended (pun intended), you will not have control over who will get the macro.  The macro would just macro the next in line or worse yet who-ever is first on the list that isn't imune.</p><p>I use the my macros on the player/class that best suits that encounter, not just the next person in line.  Yes it makes keeping track of who's imune a pain but I live with it.</p><p>IMO a better solution would be making a macro for your group by group member number but I cannot find any command that will allow for it.</p><p>Yes having to change macros is a pain and I keep several pages of JC macros for guild members and a few PuG players.</p>

[verydanger]

<cite>Onoes@Lucan DLere wrote:</cite><blockquote><p>Not to shoot a hole in your idea but .... </p><p>If your macro works as intended (pun intended), you will not have control over who will get the macro.  The macro would just macro the next in line or worse yet who-ever is first on the list that isn't imune.</p><p>I use the my macros on the player/class that best suits that encounter, not just the next person in line.  Yes it makes keeping track of who's imune a pain but I live with it.</p><p>IMO a better solution would be making a macro for your group by group member number but I cannot find any command that will allow for it.</p><p>Yes having to change macros is a pain and I keep several pages of JC macros for guild members and a few PuG players.</p></blockquote>Not having control over who gets JC actually has a benefit. When using several macros assigned to specific people, it happens that I "j-cap" someone that's out of range, immune, or even dead. With a single macro you will never do one of those things. And since your macro will have possible JC targets listed by priority, it will always go to the highest (eligible) prio target.For specific fights that requires an unusual JC cap rotation though, I'd of course create another macro and use that one during the fight instead.

[Auspex Mezbreaker]

<p>its not that hard to keep track of who gets JC and who its not refreshed on yet. I have 1 Macro for JC with 3 text lines. I also keep the normal spell up on the hot bar right next to its macro.</p><p>/group Jesters caps to %t</p><p>/raid Jesters cap to %t</p><p>/tt You now have Jesters Cap! your welcome %t. go nutz and make the raid proud!</p><p>Seeing how I have to target the person I am casting JC on this works great.</p><p> If I am unsure about someones JC timer I simply cast the normal spell on them and if it goes off I hit the macro button to send them (and the raid) the message.</p>

[Clacket]

<p>I simply have 1 macro for all Jcap stuff....</p><p>Target the intended recipient</p><p>/t %t you have been capped.</p><p>and then i have a macro that says</p><p>/tar (MT name here)</p><p>so that i am already back on the Tanks target before Jcap is even finished casting. </p><p>Why do you need to spam the entire raid force of this?  is there a reason to tell the rest of the raid or group?</p><p>And i am like the one said above I target the group member that best suits the situation.  It is not always the same order..... and i guess i just have a decent memory as to whom i capped and about when. </p>

[aelder~]

<p>Manual targetting for JCAP, while it saves you from retyping macros everytime you join a group, is very 2006.  It requires you to lose target on mob.  Even with a macro line to retarget your tank (I'd suggest <span style="color: #3366ff;">/assist MT</span> rather than <span style="color: #3366ff;">/target MT </span>but...) you are missing at least one auto-attack, perhaps a secondary swing, and hopefully not a proc, melee crit, and/or double attack.  That's why folks went through the painful process of <span style="color: #3366ff;">/useability on</span>... etc back in the day before the macro revamp.</p><p>What can you do about it to minimize retyping?  Well, if you have a fairly common raid group, keep it seperate.  Go to page 10 of you macros where you will forget about it.  Make 5 JCAP macros for your normal squad.  Label them RAID 1, RAID 2,... RAID 5 or similar (rather than the names of the folks).  Insert the names of your normal group members per usual.  If group abberates, just change the target in a button, <span style="text-decoration: underline;">not</span> the name.</p><p>Arrange your hotkeys as you would for this normal raid group.  Now type <span style="color: #3366ff;">/savehotkeys raid</span>.  Thereafter, anytime you type: <span style="color: #3366ff;">/loadhotkeys raid</span> these hot keys will load.  One key thing is not to change the name on those 5 JCAP keys (RAID 1 etc.) because the load hotkeys command gets befuddled if you change the title of that hot key in the future.</p><p>Now do the same process for any situation you encounter: solo, normal group, pick up group (i have 5 PUG JC keys for example)... I find I retype a lot less JC macros as a result of having these set ups memorized for my toon.  Since <span style="color: #3366ff;">/loadhotkeys raid</span> (or <span style="color: #3366ff;">/loadhotkeys solo</span>... etc) can also be a command line in any other macro, try putting it in a gear equip macro as well.  For example, I have macros for raid gear, solo gear, and group assist/dps gear... embedded in each of those is a <span style="color: #3366ff;">/loadhotkeys dps</span>... etc</p><p>This does not solve OPs initial issue of JCAP immunity tracking.  What I would love to see from SOE is if a casting macro could have its refresh tied to target's immunity instead of recast - like it currently has the <span style="color: #3366ff;">[ ] Primary</span> check box; add an check box for <span style="color: #3366ff;">[ ] Immunity</span> as the button refresh.  Then only the JCAP buttons would be highlighted for folks not-immune and when recast is clear.</p><p>Only other recommendation is to ask your groups to make a tell macro requesting JCAP.  They should not request it when they have immunity... make your own JCAP macro button.  In the target box, enter <span style="color: #3366ff;">%rt</span>, which will cast JCAP on whomever sent you the most recent tell.  Only issue in raid is that if warlock and brigand send you back-to-back tells you would send JCAP to most recent--there's no way to cycle back like you can with replies.</p><p>Hope it helps,</p><p>Aelder</p>