Infraction for JaMMi: People don't like you

◊ Kaubel · 05/16/08, 6:44 PM

Post: [Mage] 2.4 TC, aka Guys in Blue Dresses
User: JaMMi
Infraction: People don't like you
Points: 10

Administrative Note:

Message to User:

And I'm sick of the reports.

Original Post:

Originally Posted by Rounced

This leeway is probably in the realm of 50ms and as far as I know has never been definitively tested for or proven but is more anecdotal in existence, based on a post from the UI developer and just from how seamless the system currently functions under most circumstances.

I think that this is consistent with what I've been seeing. I'm still not 100% I trust it though. For example today I walked out of a cast to pom sheep something and it took a ridiculous amount of time for pom to register. It was like the server/client conversation went something like this (again in Jam language):
"I want to cast arcane blast"
"Ok well, have a gcd"
"Please wait towards the end of my arcane blast I need you to accept my next spell ; oh wait I've cancelled - await further instructions"
"Ok so you want me to wait at the end of your arcane-"
"POM please"
"No wait hold up what did you say before? Oh you cancelled your arc - ohhh you want to POM"

Very annoying. I'm not sure if I prefer the old system to the new one to be honest.

On a different note - (One which if they have to fix one of these two issues I'd rather they fix this one first...)
I definitely am getting frustrated with the stacking bug. In heroics I find myself just frostbolting for the purity of knowing your next cast isn't going to cost more mana than it should relative to the cast time. I suppose I can only hope that the Dev's do see it as a genuine bug and can look to rectify it shortly.
A simple work-around they could use would be to get the client to send the message, when AB is cast, "haste all subsequent spells by <insert relevant AB haste factor here> ; if the next spell you receive is not AB ; initiate a suitable delay before permitting the next cast. ie ; the AB debuff becomes a global haste / global delay function... and if you for some reason get a hasted scorch (or whatever) as a result - then you simply get a delay after it has registered and your next cast is permissable.

Thanks for the info on the spell relationship since 2.3 though.