P.S.: Also since 2.2, I get some strange lines in all versions of SCL: [Unknown] ++ "skillname". This occassionally occurs. Usually with hunters' or paladins' Auras. but only sometimes, not with all hunters or paladins... strange, uh?

P.S.: Also since 2.2, I get some strange lines in all versions of SCL: [Unknown] ++ "skillname". This occassionally occurs. Usually with hunters' or paladins' Auras. but only sometimes, not with all hunters or paladins... strange, uh?

The error is not in SimlpeCombatLog, according the the info you posted. It may be shown by SCL, due to running embedded, and SCL being the last addon to hook a function, but it is not SCL.

If you use WAU, even if it isn't showing any updates, click File -> Reinstall All Addons, and it will update all ace addons to the latest versions, which should alleviate any errors you are seeing.

The unknowns could be due to just having logged in and the game not having enough time to download the name of the player casting the buff, or could be due to the player being out of visible range, but within combat log range (if you used the option to increase combat log range)

I'm getting the 'uknown' thing in my log also. Not just hunters though, rogues and paladins etc. I notice it's right after I either log in or zone or sometimes it just happens without doing either. I'm not getting any errors with any mods and have reinstalled them all incase. Most strange. I'm also using SimpleCombatLog. Maybe some change Blizzard has done in the patch as it was fine beforehand.

Here's a screenshot with the combat log on the right and the unknown message.

Like I said, this happens when new player information needs to be downloaded, such as at login. Basically, this will happen during the entire time while your player (or any other, or an NPC) is not physically visible in the environment.

Test this out in Ironforge at a time when a lot of people are dueling, and you will see the same thing. I saw it before the patch as well.

There is nothing that can be done about it, as it is just due to the nature of downloading textures and player information into your local cache.. It takes longer to do that than it does to render the rest of the environment, so your loading screen goes away, and you see that until the game makes that player physically visible in the environment (including if they are offscreen because they are behind you and such).