search

netherspite / cc-buglist

CoreCraft NexT bug tracker
0 stars 3 forks source link

Combat log issues #2225

Open netherspite opened 6 years ago

netherspite commented 6 years ago

Issue by SuddenDeath
Monday Feb 01, 2016 at 17:43 GMT
Originally opened as https://github.com/ccshiro/cc-buglist/issues/2225

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.

netherspite commented 6 years ago

Comment by DarkenRal
Monday Feb 01, 2016 at 23:39 GMT

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

netherspite commented 6 years ago

Comment by Schaka
Tuesday Feb 02, 2016 at 14:27 GMT

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.

netherspite commented 6 years ago

Comment by DarkenRal
Tuesday Feb 02, 2016 at 14:41 GMT

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.

netherspite commented 6 years ago

Comment by ccshiro
Tuesday Feb 02, 2016 at 15:11 GMT

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.

netherspite commented 6 years ago

Comment by Evolvee
Tuesday Feb 02, 2016 at 15:46 GMT

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)

netherspite commented 6 years ago

Comment by Schaka
Tuesday Feb 02, 2016 at 15:49 GMT

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.

netherspite commented 6 years ago

Comment by SuddenDeath
Tuesday Feb 02, 2016 at 16:01 GMT

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

netherspite commented 6 years ago

Comment by Schaka
Tuesday Feb 02, 2016 at 16:09 GMT

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.

netherspite commented 6 years ago

Comment by Evolvee
Tuesday Feb 02, 2016 at 17:47 GMT

@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...

netherspite commented 6 years ago

Comment by Schaka
Tuesday Feb 02, 2016 at 19:26 GMT

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.