Quote:
Originally Posted by Caryatis
Few things, I believe that clients can't stun mobs over level 55 with their bash/kick attacks(unless an AA raises the level) which is why that particular limit is imposed. On the other hand this seems to limit the usefulness of it for later expansions so possibly this has changed but I had no proof so I went with that limit.
|
Yeah, I'm not sure why a level 80+ character would points into the Imobilizing Bash AA if it only affected mobs under level 55. The AA was added in GoD, more levels added in SoF and more in UF. Maybe they just start with a 0% chance on mobs > levels 55 and add a chance to stun from there. (I think it's 2% per level)
Quote:
Originally Posted by Caryatis
On your points...
1.) I think you are right, there should probably be a skill check or something to determine if a bash does stun(especially for kicks as they probably shouldn't stun as often as bash).
|
Older skill caps (around PoP?) had warrior bash maxing at 240, with Kick maxing at 210 (at lvl 50, bash was 220, and kick was only 149) Newer caps have bash cap at 320 (lvl 75), and kick at 275. From this, I'm not sure there's enough of a difference to use skill alone to determine chance of stunning, but I think it should be used. And I agree kick probably shouldn't stun as often as well, as a warrior using Bash and Kick could potentially stun quite a bit if they were both equally effective, and logically, I would more likely be stunned being hit with a shield as I would being kicked by someone with a lot of armor on (well, depending where they kicked me, I guess...)
Quote:
Originally Posted by Caryatis
2.) I went with the stun duration of 0 as it seemed the safest option however I do also remember bash stopping a fleeing mob so the random duration would probably be the most ideal solution.
|
This is most likely correct after reading up some more. I think everyone agreed that there's a chance for at least a short duration of up to 2 or 3 seconds (most likely 2, as I could it out in my head.. 3 seems a bit long).
Quote:
Originally Posted by Caryatis
3.) I think a stun always interrupts casting(the existence of the persistent casting AA is pretty solid proof that a stun always interrupts to me). The descriptions arent the most accurate in terms of actual code behind the gameplay, I read that as it gives you the chance to stun if the mob doesnt resist or isnt immune.
|
You're probably right. I was just having a hard time believing that a couple of paladin casting stun spells could almost completely lock down a caster if they can get stuns to land (even short duration). Persistent casting is also used to prevent interrupts due to movement, but that seems a reasonable explanation.
Quote:
Originally Posted by Caryatis
I think if you are going to remove the level cap on clients bash-stunning mobs, there needs to be a check to make sure the mob is lower level than the client or something like that.
|
I think this is reasonable. Or at least similar to the stun spell level limitations of up to like 5 levels over, but I guess a less than character level check would be simple and even across the board.
Quote:
Originally Posted by Caryatis
Also I could get behind the idea of a bash that doesn't stun has a chance to interrupt but no way should a resisted stun spell have a chance to interrupt.
|
Yeah, if it is done within the bash code, it would only affect stuns resulting from bash and kick attempts. I think the chance to interrupt could possibly result from the knockback portion of the stun? But then again, rereading that quote about the dev and the logic checks, it seems there's an actual check to see of casting is interrupted when the bash doesn't stun (separate from knockback, which I think would come later in the logic checks)
I can probably get something finished this weekend and post here, as this is something I definitely wouldn't commit myself without others looking at and approving.