Game Mechanics: Slam

[no chewie dont]

slam (possibly bash too) seems not to work right after last patch
thought it was my imagination the first few times but here it is
[You must be logged in to view images. Log in or Register.]
(no, neefin is not an ogre)

[Colgate]

UI looks classic enough to me

[Cid]

You are correct, Neefin is not an ogre. I do not have any ogres because I hate the forced ducking.

Slam might be messed up, but I happened to be looking right where you logged in so you had like 4 seconds to see me, target me, run up to me and attack. If it missed, it just missed. You only had time to get a single double-attack off on me from what I could see, so there wasn't time for more than one chance at slam, and it's not guaranteed.
It's very unlikely you could have killed me anyway, I was expecting someone to pop in.

As for bash, a couple of people I was grouped with earlier were testing it out and from what they said, bash had a high success rate on the other person of the same level. I am not sure if it was interrupting spells, but it was doing dmg.

I can't load the pic so I assume slam hit me for 1dmg but didn't interrupt gate. It might actually be a delay from my client on my shitty net. I had two Tstaff monks on Cid once, Wanyo and someone else in KC, and I managed to get gate off but when I landed Wanyo sent me a tell saying his Tstaff procced on me on his screen, but it never happened on mine. Nor did I have the stun when I landed.

Because my net is so slow it may leave something like a ghost image of me there for an instant when on my clientside the spell has successfully cast.

P.S. If you think it gives me some advantage, there is no advantage to having dialup except getting to say you are all spoiled bitches and I'm the only one on "Classic" internet. =P

[Bamz4l]

1 - u can disable auto-duck, and that's the first thing u should do....
2 - ya bash/slam used to interrupt mid-cast, none of this "let me see if I can finsh the cast" type shit. No, it would literally end the spell and put you in a very brief stun lock. the whole "regains concentration and continued casting" part should never even occur because the casting should have ended upon bash/slam landing.

[Yumyums Inmahtumtums]

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

1 - u can disable auto-duck, and that's the first thing u should do....
2 - ya bash/slam used to interrupt mid-cast, none of this "let me see if I can finsh the cast" type shit. No, it would literally end the spell and put you in a very brief stun lock. the whole "regains concentration and continued casting" part should never even occur because the casting should have ended upon bash/slam landing.

[no chewie dont]

Bash and or slam interupts cast on successful hit, even if it hits a rune
used to I mean

[Alunova]

Should interrupt only if that person has access to the bash skill.

In classic, iirc, slam was limited to 1 damage and a very small chance to interrupt unless that person also had skill in bash, which would increase the damage and stun ability of slam equally.

Shamans for example would never bash for more than 1 damage, with a very high miss rate and very low stun chance, even at 60.

[BlkCamel]

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

Should interrupt only if that person has access to the bash skill.

In classic, iirc, slam was limited to 1 damage and a very small chance to interrupt unless that person also had skill in bash, which would increase the damage and stun ability of slam equally.

Shamans for example would never bash for more than 1 damage, with a very high miss rate and very low stun chance, even at 60.

Shaman on live 99-06 and can attest that Bash is only 1 damage for non-native classes (or racial only bash). I agree that it had a high miss rate even at level 60, but from my memory a landing bash ALWAYS interrupted the cast, and in the way stated above by stopping the cast immediately. Most of the time the mob would immediately (after swing due to mob auto-attack) and usually try to recast the spell.

By having it work the way it does now, allowing caster to finish casting is allowing people more chances to attempt bash on monsters and reducing the potential # of casts a mob will make (whether successful or not). I don't know if that last bit made sense but what I am trying to say is, mobs are easier if allowed to continue casting even if that cast has a chance to re-gain concentration.


***Like to add that I believe mobs immune to stun were also immune to the interrupt effects of a bash, even if landed.

[no chewie dont]

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

By having it work the way it does now, allowing caster to finish casting is allowing people more chances to attempt bash on monsters and reducing the potential # of casts a mob will make (whether successful or not). I don't know if that last bit made sense but what I am trying to say is, mobs are easier if allowed to continue casting even if that cast has a chance to re-gain concentration.


***Like to add that I believe mobs immune to stun were also immune to the interrupt effects of a bash, even if landed.

good point i wasn't even thinking of this part
so its not just me, bash stopped working right?

[LostCause]

ive noticed on this server if the spell is about to go off like .5 secs or less and you bash you still get the spell off.