[DEV1234]Lift the delay/haste cap

[wish12oz]

Think about it like this, if your delay is 100, then in 100 you get 1 swing, if you add 80% haste, you now swing at 20, so you get 5 attacks in 100, if your haste was 90, you now attack at 10, meaning you get 10 attacks instead of 1 in 100. moving from 80 to 90 haste moves you from doing five times your normal damage to ten times your normal damage. This is sort of ridiculous and why SE capped it at 80% after the introduction of desperate blows when rune chopper DRK was just plain crazy. Asking for it to be higher than 80% is just stupid.

[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.

[Taint2]

Its not trolling, its a legitimate request. It was uncapped for most of the games existence. The 80 cap is too restrictive as it stands. Hell make it 85% but leaving it alone will continue to make DoT jobs fall behind the jobs that can equal them in delay reduction.

[wish12oz]

It was uncapped for most of the games existence.

It was uncapped and you couldn't reach it until desperate blows.

[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%.

[hiko]

mistake
1231

[Taint2]

It was uncapped and you couldn't reach it until desperate blows.

Sure, I was one of the few that ever got to swing Apoc at 93.3, it was game breaking at the time. 24k damage to kirin in 25 seconds back in 07. Haste is the most important stat/buff in this game. If every job can cap it then there is only room for the jobs that A) WS the most B) Take the most swings per round. 1 hand jobs are already taking a beating and it will continue to get worse. There is very little reason for an alliance to be made up of all WARs for damage, the delay cap is a big part of that reason.

[Taint2]

It was uncapped and you couldn't reach it until desperate blows.

Sure, I was one of the few that ever got to swing Apoc at 93.3, it was game breaking at the time. 24k damage to kirin in 25 seconds back in 07. Haste is the most important stat/buff in this game. If every job can cap it then there is only room for the jobs that A) WS the most B) Take the most swings per round. 1 hand jobs are already taking a beating and it will continue to get worse. There is very little reason for an alliance not to be made up of all WARs for damage, the delay cap is a big part of that reason.

[Alhanelem]

Haste should be capped further, not lifted. I'm sick of haste being the end all only important stat to have in games.

If you took 0 seconds to swing it would be nonstop actions and the server would crash.

fixed

[Cream_Soda]

Then play games that don't have haste at all.