I spent a lot of the morning going through this board, and wanted to get a few questions answered. (EDIT- as I find answers I will try to post them here so others will not have to go through this)
- Mods (alt, shift, control). I have a AHK toggle macro where you toggle it on, it spams until you toggle it off. Do mods work with toggles, or do you need the AHK key spammer that only works while you are holding down the key? Or is it likely some other WoW keybind overriding? I like using Xbutton1 = mousebutton4 for turning on and off the macro, so maybe ALT+MB4, CTRL+MB4, SHIFT+MB4 are keybound to something else in WoW?
Answer- I did a little testing here. First I made sure I had no keybinds to the toggle spammer key. I used MB4, MB5, and F1 for a 3-toggle spammer that I posted on page 4 here. I then went into keybinds and picked an action bar I was not using, and deliberately bound and unbound all combinations, IE ALT-mb4, CTRL-mb4, SHIFT-mb4, ALT-mb5…when you bind something it erases the previous bind. So this should have removed any conflicting assignment within WoW. I then tried a simple mod, and it did not work. So you must have to actually keypress ALT+mb4 at the same time, and even though you keypress ALT, you are using the toggle to KeyAction mb4, and it does not trigger the mod. This is not a killer, because with enough toggles you can get around having to use those mods.
- Reset feature in GSE. When you check the reset box on the right side in your macro, will it reset on target? I had one forum regular tell me that castsequence reset=3/tar works in KeyPress, but not in Sequence since the timer stuff and reset functionality only apply to KeyPress. If I check the reset box, does it reset KeyPress and Sequence when I change targets? If I only want the KeyPress to reset, should I not use the reset feature of GSE and spell it out as I have been in the castsequences of GSE?
Answer- Looked at it again last night, and I think in the current version of GSE that is a combat reset.
- Toggles and overrides- If I have a toggle spammer ON with 100ms delay (10 presses per second), sometimes I can press and hold another action button down and it will go off. For instance I noticed that Enhancement Shaman basically has the same rotation for ST and AOE, except you apply the 10s buff/debuff Crashing Storm. SO I will run my basic GSE macro on an AHK toggle, and I can say press and hold Crashing Storm, and it will go off. But it is spotty. So I am wondering, is the chance of this override going off dependent upon the delay in your AHK spammer? IE if I go down to 50ms, I bet it will not go off. If I go to maybe 250ms, I bet it will override every time. Have any of you played around with this?
Partial answer- I did not do time testing on this, but if you press and hold something while your toggle is on at 100ms delay, you will get one cast off of it. Works for some things, but not others. So in the Shaman example, this can work for Crashing Storm. I did use a press and hold AHK spammer in combination with a toggle spammer, and if you press and hold it seems to override, but frequently the code will hang. So it is best to avoid this sort of macro structure.
- Generic 2 button toggle. Seems like this is the most common need, as there are single target/AOE spammers, or builder/spender spammers, so you need 2 toggles. Here is the one I think should work, with mb4 and mb5 (lower and upper thumb buttons on the mouse). I pieced it together from stuff I have read here, on the AHK boards, and elsewhere
Answer- I modified Daxton’s 3-button toggle AHK script, and posted my rework for mb4, mb5 and F1 on page 4 here.
The ! key- seen a lot here. The way I understand it is !execute means if you are not presently executing, then execute? Supposed to be used for stances, druid forms, or stealth. But I had heard of guys putting it in for warriors in the execute phase to get more executes in rather than do other stuff. Seems counterproductive. Anyway, I was going around the block on Fury Warrior and Bloodthirst and Rampage. If you could use something like !Enrage to caveat usage of Rampage or Bloodthirst, it would make this a lot easier. If you are not Enraged, Bloodthirst or Rampage. Is this the sort of thing Blizzard deliberately disabled?
GSE macro design with the sequence step function and boss mechanics- Seems like the general sequence can be set up by either recording actions or tinkering around with a long enough sequence to get a cold start sequence working well. BUT once the boss makes you do the Hokey Pokey, all of that timing gets thrown off. You are not changing targets so there is no way to really reset the macro with a target reset. How do you design around this? Do you keep a macro ‘loose’ where you can pop in a few other things if needed and still basically preserve the loop? How do you build a good GSE macro that does well when the boss mechanics throw off the timing?
Can you use talent caveats in cast sequences? IE
/castsequence Agony, [talent:6/2] Haunt, Corruption
Would it skip Haunt in the above cast sequence if you were not talented in Haunt, or would it just hang period?
- Basic question on priority step functions.
Lets say you have a priority step function and the following sequence
/cast Shadow Word: Pain
If you are standing still, it would never cast SW:Pain right? But what if you are moving and you can not cast Smite while moving? Will it then apply Pain? Seems to be an interesting way around DoT refresh if so.
- Focus frames.
I was thinking about how to do a Discipline Priest. The basic germ of an idea was this. Have an AHK spammer punch the DPS macro on the focus target. Make a simple assist playername, set focus to that target, go to last target macro such that you could punch it and know you would get the target of another player. Every DPS spell in the macro would have a focus target caveat, and if the raid doesn’t need healing this thing just DPSs hard on the focus. But you could click other players and shield them up with mods. So in KeyPress put maybe CTRL for PW:Shield so you could shield between DPS checks. Has anyone tried playing around with spam macros on focus frames? Does it work or is it just a headache? This seems to be maybe a solution for having to watch both player frames and the field at the same time.