Ghostcrawler wrote:
These type of issues (and there are several abilities so affected) are not bugs per se. They are disagreements or just delays in between the client and server. It takes time for that communication to happen and sometimes things get offset. Talk to mages about Ignite munching for instance. We try to implement a certain amount of split-second timing, because it feels better when the game is responsive and perhaps more exciting when changes are instant. But there are real technological limitatons to what we can do.
It's not a bug in the sense that we can't fix it. It's Internet latency. If we think it is going to become a real liability for bears, then the kind of thing we can do is design around it. For example, Savage Defense could have 3 stacks that affected the next 3 hits. Dropping from 2 stacks to 1 stack because of latency mismatches would be superior to dropping from the shield being on to the shield being off. We need to get a better feel for how common the problem is and how SD is working in general before we started iterating on the design though.(Source)
It's not a bug in the sense that we can't fix it. It's Internet latency. If we think it is going to become a real liability for bears, then the kind of thing we can do is design around it. For example, Savage Defense could have 3 stacks that affected the next 3 hits. Dropping from 2 stacks to 1 stack because of latency mismatches would be superior to dropping from the shield being on to the shield being off. We need to get a better feel for how common the problem is and how SD is working in general before we started iterating on the design though.(Source)
Interesting.
I've been ignoring SD as I know it is buggy both from experience and other people's testing. This could make me pay attention to it a bit more.
Honestly, I feel it should be passive but w/e.