Skip to Content
2-05-2008 @ 1:54PM
Just as an FYI - you actually have the details backwards.Prior to 2.3, the timing was handled on the client. /stopcasting worked because it told the CLIENT to cancel the spell and let you start another, but the spell still went off because on the server the timer finished before the /stopcasting command got there. (Thats why you had to do it in that latency window, that extra time is what let the spell finish on the server before /stopcasting got there.)Now with 2.3, the timing is done on the server. If you hit the button, the client tries to send a casting request, even if you already have a spell going. The server decides if it actually goes off or not based on its timer.Other then that, this is good information for all casters, and not just healers. People running on 200ms connections can start a spell before their current spell is actually finished so long as they time it right to get a speed boost, and not everybody knows that.
First time? A confirmation email will be sent to you after submitting.
Members enter your username and password.
Enter your AOL or AIM screenname and password.
Please keep your comments relevant to this blog entry. Email addresses are never displayed, but they are required to confirm your comments.
When you enter your name and email address, you'll be sent a link to confirm your comment, and a password. To leave another comment, just use that password.
To create a live link, simply type the URL (including http://) or email address and we will make it a live link for you. You can put up to 3 URLs in your comments. Line breaks and paragraphs are automatically converted — no need to use <p> or <br /> tags.