search

ccshiro / cc-buglist

Corecraft's issue tracker
43 stars 40 forks source link

Combat log issues #2225

Open Klimpb opened 8 years ago

Klimpb commented 8 years ago

https://www.youtube.com/watch?v=KQbE8qvJTv0 -Blind resisted? But no info. Combat log sometimes doesn't report spell resists, dispel resists, etc.. Not sure why this happens.

DarkenRal commented 8 years ago

It's miss actually, not resist. Rogues can't resist Blind but he had Evasion buff.

Schaka commented 8 years ago

It's supposed to display "Miss" anyway.

I've noticed that there are also issues with SPELL_DISPEL events not firing (and resists to dispels accordingly). That sucks ass, to say the least. But I haven't gotten around to test thoroughly and create a proper bug report.

DarkenRal commented 8 years ago

It's supposed to display "Miss" anyway.

Mostly yes, but also happend on retail that you couldn't see what happend to your Blind in floating combat text. Dunno if combat log reported anything in such situations. But ofc it's a bug and should be fixed if it's possible.

ccshiro commented 8 years ago

The miss message showed up for me: http://i.imgur.com/B6oaDuX.jpg

My guess it is a scrolling combat text bug (it did bug and miss events or delay the printing of them sometimes @ retail too).

Preferably someone can check/verify that the combat log event is always properly triggered, and that this is indeed not a server bug.

Evolvee commented 8 years ago

This happened to me few times as well...enemy resisted blind/kidney shot but the interrupt bar didnt notice anything(but might be just a bugged addon)

Schaka commented 8 years ago

There has always been a problem with the Combatlog getting stuck and bugging out. You can prevent this with a simple macro: local f = CreateFrame("frame",nil, UIParent); f:SetScript("OnUpdate", CombatLogClearEntries);

If you have this activated and still get missing combatlog messages, the issue is with the server somewhere.

Klimpb commented 8 years ago

@Schaka I'm using "Combat log fixer", I'm guessing it's doing the same & a little more as that macro?

Schaka commented 8 years ago

CombatLogFixer does not do the same thing. It will keep your combatlog in tact (so that you can read it) until it realizes it's been broken. So things like the above will still happen, albeit much less frequently.

Evolvee commented 8 years ago

@Schaka Im clicking on /script CombatLogClearEntries() before every start of arena, so it should be enough right? But what if it bugs right in the middle of arena...

Schaka commented 8 years ago

It's not enough. If it breaks in the arena, you need it to get fixed again. Use the macro I posted once when you log in or make it an addon. Your combatlog will not be readable, but events will still fire and addons won't bug out.