[2008/04/13 23:16:29-3913-x1]: Parrot-r69536\Data\CombatEvents.lua:1428: Bad argument #2 to `RegisterCombatEvent'. localName must be a "string", got "nil".
Parrot-r69536\Code\CombatEvents.lua:1092: in function `RegisterCombatEvent'
Parrot-r69536\Data\CombatEvents.lua:1428: in main chunk
the error posted by vargr is easy to find. with your last svn update you deleted the area checks to all pet events. now you are trying to handle some of the pet events as player events.
Pet events were handled as player events before. The result is that it is displayed as player-event.
I deleted the areachecks because I added the missing events (Incoming Pet Melee Immunes, etc)
The events called in the posted errors are all registered in the Data/CombatEvents.lua so a possible explanation would be that they aren't registered properly. I've tried with German Client (with empty SavedVars), and the error didn't occur to me.
Also I never touched the "Party killing blows" in Code/CombatEvents.lua:2201
but as i said in my edit. i don't think it's a good idea to show pet incomming events as player events
That's right. That was the case with your fix in the first post (first thing that came to my eye after being absolutly amazed that Parrot worked again).
Incoming damage on the pet, showed as incoming damage to the player. So I added new CombatEvents for incoming pet-dmg/heal etc. so it can be dealt with elsewhere.
This "spam" can be turned off easily in the events/incoming menu now.
(I like that spam, others don't like to see Selfheals in outgoing _and_ incoming, that's what options are for ;) )