ZOS_GinaBruno wrote: »Sorry for the delay, everyone! We do have some movement on this bug (no pun intended). We're currently testing a fix for this issue that we plan to include in one of the PTS patches to further test. Currently, it's looking like it'll be the 3rd PTS patch (so not the one coming up this Monday, but the one after that).
Sure thing, because it's annoying.BlackbirdV wrote: »Someone explain to me what the bug is?
BlackbirdV wrote: »Ok so reading threads about this bug... Why are you even complaining? You do realise, it's not gonna get fixed unless you provide information. "fix this it's a bug" gives no indication.
With 100 000's/millions of lines of code, it makes it a horrible task to find the bug. If reporting bugs format, then it with points, evidence, notes etc.
Such as this:
Bug
What the bug is.
Explanation
Now explain what the bug is
Evidence
Show evidence of this bug (pic, gif video x10000 better)
Additional information
What sets were you using? Where did this bug occur? What was Latency like? What CP passives have you got? What buffs did you have on? Has this occured anywhere else? If so, make another report (Same thread, please, for consistency and cleanness)
Notes
Additional notes.
If going for another report on it, do something like this:
Explain
Furthermore explain this bug.
Evidence
More evidence
Additional information
Same as above, maybe there's a pattern forming... maybe there's a certain skill making it bug..?
Notes
Not Natch potes
Theory
Nothing wrong making a theory with collected evidence and knowledge. This helps devs A LOT as it takes time off their hands since you're doing it.
PelinalWhitestrake wrote: »Broccoli Lesnar broke the streak.