I'm hoping that new swing timers will be a lot more reliable with the upcoming changes that Blizz are making to the combat logging system. Rather than having to parse the text of the combat log, it'll be possible to react to events from the combat log data stream, so should be way better.
Charsi, I'd personally be very interested in this hack of yours. Could you possibly put it up somewhere for download, i.e. sendspace?
Sure, no problem. Since others will be using it i'll try and make it a little bit more robust.
Try this link from sendspace - I updated it tonight to handle back to back ss/wf procs and back to back cleave/HS spam. Place the file in your Quartz_Swing mod folder. Back up your Swing.lua file first. This does not address haste procs, but I might try that in the future
Edit #2: took it for a spin through a full Hyjal clear, no problems with the swing timer. It feels a lot better, though flurry is still throwing it off some if you have good flurry uptime it's liveable.
Last edited by Charsi : 12/21/07 at 12:57 PM.
Reason: added link to swing.lua; simplified content
I tried 2H dps for the first time last night (WWS) and I must admit it was a lot of fun. Managing the timing of Slam rotations was an entertaining change of pace and I hope to try it in a real raid next week in BT/Hyjal after all of our regulars are back from the holidays.
That all being said I have a question. A few times I missed hitting a Slam immediately after a white swing due to having to move or just waiting on the GCD. If I've missed a Slam and am now halfway through my next swing bar, should I wait for the next white atteck and resume the roation at that point or just Slam immediately? I was letting the white attack go through for the most part unless I had a full rage bar but I'm not sure if that was the right decision.
Slamming mid swing will make your next white hit a very long duration away. Up to 5 secs assuming a 3.6 weapon (3.6+1.8). This also means you have delayed the next potential WF proc as it only goes off white hits and on-next attacks these days.
My suggestion would be to cue HS for your next white swing, since you did not slam you can fit a slightly higher threat move in to absorb the dmg you did not do from a Slam, plus HS gets all the attendant benefits of a special (can't glance etc). Then settle right back into your slam rotation, as the swing timer and cooldown cycle you are on would still be in place. Cue HS, and use the GCD you have till the next swing to refresh a shout or a debuff perhaps, makes it useful without having to restart your rotation.
I may be very wrong, others will advise if so, but that's what I would do.
If you're halfway through your swing timer, you should be hitting MS or WW at that point, making sure GCD has cleared by the time next white hit occurs, so you can slam again.
Not much in it really. It depends on personal preference. Some people have trouble dealing with slam rotations with sword spec, due to the procs causing most swing timers to reset.
I just picked up a CE and am trying to get back into the swing of things (pun only slightly intended). With the 3.5 speed, how much flurry is optimal? I was a little leery of maxing flurry so trying a 31-30 build with 2/5 flurry and 2/2 imp execute and 5/5 commanding presence vs 5/5 flurry, 0 in imp execute and 4/5 commanding presence.
This is a computer-generated message and needs no signature.
Has anyone done the math between a 21/40 (one point more in 2H Spec) and a 20/41 2H Fury Spec? Rampage is pretty suboptimal for a Warrior using Slam all the time, you either lose a BT/WW or a White Hit every 30s or so.
I just picked up a CE and am trying to get back into the swing of things (pun only slightly intended). With the 3.5 speed, how much flurry is optimal? I was a little leery of maxing flurry so trying a 31-30 build with 2/5 flurry and 2/2 imp execute and 5/5 commanding presence vs 5/5 flurry, 0 in imp execute and 4/5 commanding presence.
I assume if you're only going 31/30 that there is another warrior providing BF for your raid? That debuff really is the big reason to go the arms route with a 2H weapon. Generally speaking at the higher end of raiding BT will do more damage than you will get out of MS. Hell its only really at around 3000 ap or just over when raid buffed in your MS spec that BT will do more dmg.
As for your current question do you DW with 2 fast weapons when it comes down to execute range? If you don't then imo 2/2 imp execute is a waste of points. You'll be able to execute once every 3.15-3.5 secs if you're not DWing and generally thats lower dps than your normal slam cycle. Obviously Heroism will help with your executes and if you do go DW you will only need 10 rage every 1.5 sec to spam execute.
How much Flurry can you handle is all down to your reactions and pc connection really. 2/5 Flurry means you will be running a 3.15 speed wpn when flurried (assuming no other haste and I'm too lazy to check your armoury) which gives you an error of 0.6 sec to use your instant and be able to get a slam off again. I would think 4/5 is doable with a decent connection and normal reactions but I find the 3/5 Flurry I use (I'm the BF supplier) works very easily with my rotation and if I could run 4/5 I would, although I have a 3.6 sec wpn. My connection can be a bit temperamental so I prob wouldn't go the full 5/5 if I was doing 31/30 or 20/41 spec.
Sure, no problem. Since others will be using it i'll try and make it a little bit more robust.
Try this link from sendspace - I updated it tonight to handle back to back ss/wf procs and back to back cleave/HS spam. Place the file in your Quartz_Swing mod folder. Back up your Swing.lua file first. This does not address haste procs, but I might try that in the future
Edit #2: took it for a spin through a full Hyjal clear, no problems with the swing timer. It feels a lot better, though flurry is still throwing it off some if you have good flurry uptime it's liveable.
Thanks a ton for the upload. I finally had a chance to do some PvE and I can't ever recall the swing timer throwing me off on my slam rotations, running 33/28 with a 3.6 weapon. Your modified swing timer combined with the latency fix did wonders for narrowing down that gap between landing the white hit and starting the slam.
I took Charsi's modified swing.lua and added code to listen for haste buffs gains/fades such as Flurry, Bloodlust and the generic 'Haste' buff that comes from stuff like DST/Dragonstrike/etc. When it detects a buff going on or off it updates the swing bar's length and duration on the fly.
It's not perfect but it really helps in cases such as the last charge of flurry being consumed on a swing and the next swing having the flurried speed show on the swing bar even though it is actually swinging at the non-flurried speed, making you cast slam earlier than you should and clipping the swing. Or in the case where you are swinging without flurry and then you crit an MS while auto attack is still cooling, gaining flurry and a faster attack speed yet quartz still shows the non-flurried speed until your next swing, making you miss the slam window.
I took it for a spin last night through Hyjal and some of BT and it was pretty helpful, left me wondering why I haven't done this sooner so I decided to share it with people in this thread and see what experience they have with it or any ideas on how to improve it.
does anyone know if intercept resets your swing timer?
I can tell you from PvP experience that it does not. In fact--and this is very apparent on fights like Kaz'rogal where you get stunned halfway through a swing for like 2 seconds--stuns don't reset your swing timer either.
I took Charsi's modified swing.lua and added code to listen for haste buffs gains/fades such as Flurry, Bloodlust and the generic 'Haste' buff that comes from stuff like DST/Dragonstrike/etc. When it detects a buff going on or off it updates the swing bar's length and duration on the fly.
It's not perfect but it really helps in cases such as the last charge of flurry being consumed on a swing and the next swing having the flurried speed show on the swing bar even though it is actually swinging at the non-flurried speed, making you cast slam earlier than you should and clipping the swing. Or in the case where you are swinging without flurry and then you crit an MS while auto attack is still cooling, gaining flurry and a faster attack speed yet quartz still shows the non-flurried speed until your next swing, making you miss the slam window.
I took it for a spin last night through Hyjal and some of BT and it was pretty helpful, left me wondering why I haven't done this sooner so I decided to share it with people in this thread and see what experience they have with it or any ideas on how to improve it.
I used Magey's modified swing.lua last night and tonight in SSC and TK and had no issues with timing my slams through sword specs, 3/5 flurry, and windfury procs. As for the actual DPS, that's another story entirely, as this week marks the first time I've raided. I know that the spec is viable, and I don't think my stats are below par for tier-5 raids, but I had difficulty keeping up with the other DPS on boss fights. I think the largest margin was from playing it too safe in threat on certain fights, and not using HS when I could have (+50 rage situations).
swapping out the old swing.lua for magey's didn't work for me
when i /quartz to the options menu, swing is no longer listed, and a swing timer doesn't show up when i attack something.
swapping back to my backup swing.lua, everything returns to normal. what's up?
Maybe you are using an older version of Quartz? Charsi's file worked with my version when I replaced it and I usually update my Quartz from WowAce every few weeks. Try getting the latest 'official' version from wowinterface and see if it helps.
That seems like a really old version; the current version on wowace is 56xxx. And I just checked wowinterface and the 'official' Quartz version they have is pretty old as well. You might wanna try getting this instead http://files.wowace.com/Quartz/Quartz.zip
I just switched over from SwingTimer to Quartz because of Charsi's modded version, but often the timer just disappears for a swing or two. Is this common?
Here is a question, do most people use the time remaining on Quartz swing timer to judge when to slam? if so, does anyone know a way of making the text of the time remaining larger w/o making the bar rediculously large? If not is there a better way of judging when to swing.
12/19/07, 11:42 AM
Similar Threads
