[DEV1234]Lift the delay/haste cap

[CrystalWeapon]

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.

It depends on the number of attacks that you would need to process before the mob died, how many individuals are doing it at once, and how many people are nearby to see the damage. It would be the sheer number of attacks in quick succession that would have to be broadcast all at once to all individuals within range that would cause anything from massive lag to a complete network failure.

Even if the cap was 100%, haste would never truely be 100%. Like an infinite loop with no delays, it would always be limited by the processor that's computing the data. It's not as bad as a divide by zero error, but it's still pretty damn bad because of the fact that all the data has to be sent out exponentially to all individuals within range. I'd compare it to running several GOTO 10 programs on one server at the same time that all broadcast data across a network.

Note: I'm not arguing with you. I just felt like putting in my two cents because I'm a nerdy code monkey. Tech and programming talk makes me geek out.

[Korpg]

The damage done is instantaneous, that is why when you have 8 swings that will kill the mob on the 8th hit, the mob doesn't fall to the floor until the 8th hit, but the HP bar goes down to 0 before the first swing happened. Having 100% Haste means that you have 0 delay, which makes all melee hits go back to back instantly, making the HP bar go from 100 to 0 regardless of accuracy (because a missed hit still has 0 delay, so you can have floored accuracy and still instant kill any mob). Even with 99% haste and 5% accuracy, the mob will die in less than 5 seconds.

[Byrth]

Totally irrelevant, but the point was that you'd be necessarily limited by processor speed because the system is discreet. Think of it like this:
1) Every cycle, the program checks to see if you're going to attack this cycle based on your delay and the last time you had an attack round. Like, imagine it cycles once per 1 delay.
Imagine you have an effective delay of 91 and have just swung. Your counter starts at 0, and every cycle it will increment by 1 and be checked with "Is the counter greater than or equal to 91?" No? Continue. So for 90 cycles it will come back as "no," but the 91st cycle will come back as "Yes," you'll attack, and it will reset the process.
2) If your delay is 0, every cycle it will come back "Yes, his counter is greater than 0." So you attack.

CrystalWeapon's point is that this isn't truly dividing by 0, and you don't have an infinite attack rate, because you're limited by how quickly the processor "cycles." Not incredibly relevant (as it's close enough to an infinite attack rate), but we don't have to worry about dividing by 0.

[Korpg]

I'm just wondering what is the point in debating on this anyway?

SE won't raise the haste cap past 80, we should all hope that they don't lower it to 75.

[Greatguardian]

I'm just wondering what is the point in debating on this anyway?

SE won't raise the haste cap past 80, we should all hope that they don't lower it to 75.

Well, even if they uncapped total delay reduction, we'd never hit 100% anyways so really it's a matter of theory either way. Haste itself will never break 93.3% (25% Gear, 25% JA, 43.3% Magic individual caps), and its relationship with dual wield/martial arts/etc is multiplicative so you're not going to end up hitting 0 delay.

80% is just a cap that almost any job can hit, whereas 93.3% is only attainable by DRK.

[Korpg]

Wouldn't the cap be 83.3% if they do uncap it?

[Cream_Soda]

Wouldn't the cap be 83.3% if they do uncap it?

Desperate blows, Drk.

[Korpg]

I meant for every other job but DRK.

43.3% Haste from Spells
25% Haste from Gear
10% Haste from Hasso (maybe throw in a DNC too?).

Since DRK can easily cap haste from JA, we will throw that out of there.

Edit: I don't know why, but I keep forgetting Hasso for some reason.

[Supersun]

Well technically 100% haste isn't possible since your attack speed would be undefined, but yes, as haste approaches 100% your attack speed approaches infinity.

[Byrth]

You should look at this post, Korpg. I didn't format it very nicely, but all the information is there.