Event changes in Legion
 

See this thread for diffs: http://www.wowinterface.com/forums/s...ad.php?t=53455

There any lists I can look into?
UNIT_SPELLCAST_START returns different info than live. Having a hardtime finding what it is.

SpellID is not a spellID anymore.
Here is the info I got back from the event.
This is for Solar Wrath spellID 190984

Unit: player
Name: Solar Wrath
Rank: Solar
LineID: 3-2084-1-152-190984-00001D7EA8
SpellID: 569608

Edit: With more testing the last set of digits on the lineID changes when casting over and over. There must be a function to parse the lineID. The SpellID is a random number each time. So its most likely a useless parm now.

This is retaded, we seriously have to parse a guid string just for the spellID?

We decomposed the new UNIT_SPELLCAST_* GUID some time ago, this is the layout:

3-[server id]-[instance id]-[zone uid]-[spell id]-[cast UID]

So yes, you need to parse this GUID to get the spell id. The cast UID is unique to every single spell cast.
What the last parameter is on the U_S_* events is not yet known. It looks like flags of some sort, but I was unable to determine their meaning.

The GUID has a bunch of advantages, it allows you to clearly group spell cast events together, like the appropriate start with the success or cancel, or whichever.
The previous method the old events offered was generally not very reliable.

Interestingly the FrameXML UI itself seems to not have been updated to properly use these new events.

You could have easily do this before. Each cast has an unique cast lineID, channeled spells had 0.

Now if you dont pase the guid, and just compare as a whole. That could potentionally cause some issues:

1. You start casting a spell.
2. You zone into a new zone.
3. Every stop, success, interrupt, event will fail because the GUID wont be the same.

And since it seems like you will be forced to parse, then it will be so heavy resource wise.

I recently reported a minor issue regarding the lineIDs, i wonder if this would be their potentional fix for it. But honestly this would even cause more issues then it fixes.

Is this also true for UNIT_SPELLCAST_SUCCEEDED? In WoD the lineId does not return a GUID, so I assume if UNIT_SPELLCAST_SUCCEEDED has changed in Legion we need to special case processing based on release.

The lineId was not very reliable.
Splitting a string at a pre-determined deliminator isnt actually an expensive operation, so complaining about resource costs isnt really worthwhile. The alternative probably is that the game applies this split, so nothing saved.

All the UNIT_SPELLCAST_ events have changed to this layout.

UI_ERROR_MESSAGE: number, message

not sure what the number means, because it's not unique - maybe a category id?

some samples:

252 Another action is in progress
50 Can't do that while moving
50 Interrupted
51 Item is not ready yet.
220 You have no target.

I recently wrote a castbar addon, and i havn't run into any issues with the lineID method. And everything works perfectly.
Well it's not that expensive, i just don't see whats the point storing everything in a big string instead of proper values. Specially on something that gets called bazillion times.

So for a proper lineID I need to take the last set of digits from the spellGUID?

Be nice if blizzard had docs on this. Right now I use combatlogunfiltered for spell missed, energized, failed.
If the new spellGUID has all the info now, thats actually useful. But I couldn't find any lua code using the new lineID format.

Thats a totally different thing. These are only cover when you start/stop/fail/succeed with a spellcast. The miss/parry/dodge/evade/glacing/crusing/crit/multistrike events came after the spell hits the target. And you still gonna need different events to track those.

Since you're parsing spellID from a string. The spellID will be of type string. and you'll have to turn it into a number by doing tonumber(SpellID). Found this out yesterday why it wasn't finding the spell in my table after an hour.

3 global calls just to get an info from the guid, and the strsplit is basically a for cycle which goes through the whole string:

You don't need to (and shouldn't) use select.

Yeah you can ditch the select for some extra variables, i only wanted to show a more compact approach.

While more "compact", it is slower. Which especially matters in combat.

Which events are used for learned appearances and for the new class spells you get when your demon hunter kills a certain quest npc?