Duck/cancel

[Lojik]

How come it has Taken so long to fix this?

[Gustoo]

Originally Posted by Lojik [You must be logged in to view images. Log in or Register.]

How come it has Taken so long to fix this?

[indiscriminate_hater]

Typical BDA exploit

[Whiteberry]

Originally Posted by Lojik [You must be logged in to view images. Log in or Register.]

How come it has Taken so long to fix this?

I see what you did there,

[maskedmelon]

For Green99, how 'bouts we eliminate the ability to weave spells between combat swings too? That's not classic either, but I think it was originally patched to current mechanic some time around pre-Velious launch patch. Will research...

[kaev]

Originally Posted by maskedmelon [You must be logged in to view images. Log in or Register.]

For Green99, how 'bouts we eliminate the ability to weave spells between combat swings too? That's not classic either, but I think it was originally patched to current mechanic some time around pre-Velious launch patch. Will research...

wut??

It wasn't 100% reliable, due to latency, but it wasn't impossible either. Before I worked out that Yaulp was nigh useless I was Yaulp'ing between swings on my original paladin on live in the summer of 1999. I hand parsed my logs at the time to verify that it worked fine with a nice long delay 2hander. (Logs were great in early vanilla because they were the easy way to monitor your numerical skill value, the messages disappeared in combat spam and your Skills window only showed the vague text and no numbers)

A lot of people misunderstood (and still misunderstand to this day) the interaction between auto-attack and spell-casting in original EQ. Spell casting did NOT "reset" your melee swing delay, the mechanics were completely independent. BUT, since you could not attack if you were casting, when the melee swing cool-down expired the attempted attack reset the cooldown timer. This is exactly what happens when you make a swing attempt at a mob you cannot see, or at a mob that is too far away, or at yourself, or at another player character or player character pet. You got no red message saying why your attempt to attack failed, just as you got no message when you attacked another player or a player pet.

The change (mid-Velious? can't recall) was that, for hybrid spell-casters ONLY, if your melee attack cooldown expired mid-cast with auto-attack active, instead of negating the attack and restarting the cooldown your attack was delayed until the cast finished.

This change was a big help to hybrids who did not understand the mechanic or were too lazy tap a key before and after casting to toggle auto-attack. For those of us who had worked out the mechanic and used our knowledge (there was a discussion on alt-games.everquest) it just saved a couple keypresses to turn auto-attack off/on before/after you cast during combat.

[maskedmelon]

Originally Posted by kaev [You must be logged in to view images. Log in or Register.]

Spell casting did NOT "reset" your melee swing delay, the mechanics were completely independent.

That is the way things work now and worked post this patch:

http://everquest.allakhazam.com/hist...es-2001-1.html

January 9th, 2001 3:00 am

"Melee attack timers will no longer be reset when a SK, Paladin or Ranger casts a spell. Previously these classes had to wait a full attack delay after casting before they would attack via melee again."

:/

[kaev]

Originally Posted by maskedmelon [You must be logged in to view images. Log in or Register.]

That is the way things work now and worked post this patch:

http://everquest.allakhazam.com/hist...es-2001-1.html

January 9th, 2001 3:00 am

"Melee attack timers will no longer be reset when a SK, Paladin or Ranger casts a spell. Previously these classes had to wait a full attack delay after casting before they would attack via melee again."

:/

Neither the first nor the last time a patch note gave an incorrect description of an EQ game mechanic. Accurate communication never was a priority at Verant/SOE. Also remember that these are the same people that insisted the Alchemy was working as intended when it was impossible to skill-up due to the initial buggy implementation. The people writing the patch notes for the players were often a clue or thirty short when trying to communicate something they misunderstood from a dev.

[edit]
Note that the patch note is not completely incorrect. The first sentence is true and no doubt came direct from the dev who changed the client code (attack delays are client-side, you knew that, right?). The second is false and doubtless was a "clarification" added by some manager or community relations person.
[/edit]

[Uuruk]

You won't be getting a response from a dev on this and if you do they won't be taking it out.

Anyway back to my pet getting charmed.

[Ravager]

Originally Posted by maskedmelon [You must be logged in to view images. Log in or Register.]

For Green99, how 'bouts we eliminate the ability to weave spells between combat swings too? That's not classic either, but I think it was originally patched to current mechanic some time around pre-Velious launch patch. Will research...

When I first started playing in classic before Kunark, my friend explicitly told me to try to time my casts between swings.