[DEV1234]Lift the delay/haste cap

[Taint2]

With every other "cap" lifted like crit,crit damage,fast cast etc. Its time to get rid of the 80% cap on delay reduction. This will help out a number of jobs from the buffers (COR,BRD,Hasters,DNC) to all the DDs that can break the 80 mark. When the 80 cap was implemented FFXI was a very different game. 5k WS were unheard of (let alone the 10k plus ones) DoT was a major factor and zerging was a common strat. Now that things have changed its time for to lift the overall cap. Individual caps should be kept, 25 in gear, 25 in JA, 43.3 in magic etc.

[Korpg]

With every other "cap" lifted like crit,crit damage,fast cast etc. Its time to get rid of the 80% cap on delay reduction. This will help out a number of jobs from the buffers (COR,BRD,Hasters,DNC) to all the DDs that can break the 80 mark. When the 80 cap was implemented FFXI was a very different game. 5k WS were unheard of (let alone the 10k plus ones) DoT was a major factor and zerging was a common strat. Now that things have changed its time for to lift the overall cap. Individual caps should be kept, 25 in gear, 25 in JA, 43.3 in magic etc.

Why not ask for brews 100% of the time.

Cap at 80% is fine as is. If you want cap to be at 100+%, then what's stopping you from asking for 300% TP all the time, because that is what you are going to get....

[Elexia]

Yeah, give us Brews with ISP, AN and CP while we're at it.

[hiko]

yes give DRK 100% haste with their new JA that inhibit TP gain (since with100% haste the 2sec delay after WS will be a bigger lost in dmg than not wsing)

[Elexia]

yes give DRK 100% haste with their new JA that inhibit TP gain (since with100% haste the 2sec delay after WS will be a bigger lost in dmg than not wsing)

This would actually be a good adjustment for DRK.

[Cream_Soda]

yes give DRK 100% haste with their new JA that inhibit TP gain (since with100% haste the 2sec delay after WS will be a bigger lost in dmg than not wsing)

Not really, the mob would be dead far before you ever even get the chance to consider ws'ing, lol. 100% haste is infinite attacks.

You'd spend more time engaging and disengaging than doing anything else, lol

[RabidSquirrel]

Not really, the mob would be dead far before you ever even get the chance to consider ws'ing, lol. 100% haste is infinite attacks.

You'd spend more time engaging and disengaging than doing anything else, lol

I'd be willing to bet 100% isn't infinite. It all depends on if they allow more than one attack via auto-attack per frame, which I doubt they do.

[CrystalWeapon]

I'd be willing to bet 100% isn't infinite. It all depends on if they allow more than one attack via auto-attack per frame, which I doubt they do.

100% haste would indeed be infinite. The % is subtracted from your delay. If you take say 6 seconds to swing, at 80% haste you would take 1.2 seconds to swing. Which would be as stated earlier 5x your normal actions at 80% haste. At 90% you would take 0.6 seconds to swing. 10x your normal actions. The haste formula is one that approaches infinity the closer you get to 100.

If you took 0 seconds to swing it would be nonstop actions and the mob would die in an instant. If you imposed a restriction on how often an autoattack can initiate say 0.1 seconds is the lowest it could possibly go, then it's not truely 100%. For the 6 second swing example you would only have aprox. 98.3% haste, so it would never truely be 100%.

[Atomic_Skull]

100% haste would indeed be infinite. The % is subtracted from your delay. If you take say 6 seconds to swing, at 80% haste you would take 1.2 seconds to swing. Which would be as stated earlier 5x your normal actions at 80% haste. At 90% you would take 0.6 seconds to swing. 10x your normal actions. The haste formula is one that approaches infinity the closer you get to 100.

If you took 0 seconds to swing it would be nonstop actions and the mob would die in an instant. If you imposed a restriction on how often an autoattack can initiate say 0.1 seconds is the lowest it could possibly go, then it's not truely 100%. For the 6 second swing example you would only have aprox. 98.3% haste, so it would never truely be 100%.

If it wasn't capped somewhere what would happen is that 100% haste would cause a literal "divide by zero" situation. Whenever someone achieved 100% haste and attacked something the server software would lock up. I think what happened was that the whole issue went unnoticed until people started getting dangerously close to 100% haste and they went in with the intention of just capping it at 99% or something. But once they took a good look at it they said "holy %#&@ that's overpowered" and implemented an 80% cap.

[Korpg]

Hundred Fists for everyone! Nothing will survive longer than the time it takes to engage!

[Removed by Moderator according to the FINAL FANTASY XI FORUM Guidelines.]