Autofire

eqjenius said:
Can you clarify: you're saying the refresh timer is still capped even though we're not physically mashing the ranged attack button anymore, correct?
Click to expand...
No, read the part of that quote you edited out. You're no longer subject to the button refresh limitations because you're not pressing the button.
 
Rorne said:
No, read the part of that quote you edited out. You're no longer subject to the button refresh limitations because you're not pressing the button.
Click to expand...

I'm not convinced that's what Zae was saying. If rangers are no longer haste capped due to client limitation, that makes this a pretty hefty DPS upgrade across the board. Not that I would complain, just seems unlikely :p
 
That is what she is saying, and I think it is accurate considering I parsed very well during our raid today. Not that I feel that my DPS is now overtier for how geared my toon is...

And like robby I did notice that I generated a lot more aggro. I pulled mobs off Drakie when he was tanking with a shield twice.
 
Last edited:
Ranger i was grouping with was pulling hella agro last night over a pretty good wizard and monk. He figured it was just increased DPS that he wasnt accounting for with jolts.

Autofire ftw
 
eqjenius said:
I'm not convinced that's what Zae was saying. If rangers are no longer haste capped due to client limitation, that makes this a pretty hefty DPS upgrade across the board. Not that I would complain, just seems unlikely :p
Click to expand...

You're misinterpreting in at least two places.

As near as I can tell, and someone else seemed to confirm independently a few days ago which is what made me decide to put autofire now, the Ranged Attack button will only refresh in full-second increments, rounded up. If you had a 53 delay bow and no haste, you essentially had a 60 delay bow. There wasn't a haste cap, but for the same reasons any amount of haste that didn't bump your delay over a full-second threshold was doing nothing for you. 77% haste might bump that bow down to 3 seconds (5.3 / 1.77 = ~2.99 = 3 seconds for the button) but you'll need another 88% to bump you down to 2 seconds (5.3 / 2.65 = 2), anything more than 77% and less than 165% would do nothing. This is a big reason why low delay bows sucked.

The client will only send the packet saying you hit the Ranged Attack button to the server if the button was not greyed out, so there wasn't really any way to fix this otherwise. Autofire fixes this by circumventing the button and its clientside stupid timer altogether in favor of a flexible and precise serverside timer which can account for every little point of delay and haste.

edit: I guess there was a delay cap in the sense that real delay couldn't go below 1 full second with the button, but not many bows could get there in the first place.
 
Last edited:
You are amazing.

Does backstab operate the same way? Or is the 100% haste cap on the BS button a completely different matter.
 
Yes I too noticed one of the first responses to "hey archery is a fair bit better now" was "okay but is it going to be more better?"

I dunno. Maybe with a nerf for the difference. Depends where archery DPS is nowadays.
 
Also ask Marza, he's the one who decided overcap Dual Wield and Double Attack should do stuff in the first place.
 
Zaela said:
Yes I too noticed one of the first responses to "hey archery is a fair bit better now" was "okay but is it going to be more better?"

I dunno. Maybe with a nerf for the difference. Depends where archery DPS is nowadays.
Click to expand...

To be fair Kedrin is the highest tier active ranger and he has always been upset, as most of the high tier loot has DW or DA mods on them and they do nothing for his primary form of DPS. And also that blazewind will not drop a friggin bow.
 
I think Blazewind has to die to drop loot. Someone who has killed him before might want to verify that, though.
 
Hey zaela i found a bug: when you start firing, you can invis, then it doesnt wear off if you continue firing.
 
Something i have noticed with my shadow shuriken's specifically on sorrow but could swear on a few other things, Is that the range i can throw them at isn't the same when auto-firing vs mashing my ranged button, On sorrow specifically i can stand on the shore and hit him mashing the button but i am oor for auto-fire
 
I can't tell how the client determines the max range for throwing. Archery uses bow range + arrow range. Autofire for archery uses bow range + arrow range, for throwing it uses the range on the thrown item. Dunno what to say there.
 
Its possible the client was doubling throwing weapon range (like counting range slot as a bow and ammo as an arrow and adding both together)
 
just a minor graphics issue, not sure if others have same problem. any way to make the bow auto appear when you autofire? like when you hit the ranged button.
 
just hit the range atk button, it helps if you do /assist off ( in chat bar not hotkey) and you will not auto atk on assist so you wont have to hit the button everytime to make your bow appear.
 
You must log in or register to reply here.
Back
Top Bottom