Pull Warning 

Behaviour
Pull Warning generates a warning message when an enemy is
pulled.
To issue a real Raid Warning in a raid, the player with the
addon needs to be a raid officer.
For a direct pull names of the pulling character and the enemy
are displayed. When the player simply enters combat a generic
pull warning is issued.
Since the addon traces the combat log and checks if the player
is entering combat, just one active copy of the addon should be
sufficient for the whole party or raid.

Installation
Simply copy the PullWarning folder to the Addon directory of
your World of Warcraft installation.

Usage
Pull Warning is deactivated by default as some might consider
it to be chat spam.
To enable Pull Warning simply type:
/pullw on
To disable it again type:
/pullw off
(This setting is saved per character.)

For those who want to enable/disable Pull Warning with a macro
there is the following command:
/pullw toggle

As Raid Warnings are no longer possible in a party, Pull Warning
is able to optionally simulate these. To toggle this feature use
this command:
/pullw fakerw
Pull Warning still uses Raid Warnings if possible, so make sure
you are a Raid Officer if you want the real deal.

The "force" option enables a pull warning for the next pull
by the player even during combat (normally the addon is deactivated in that phase).
This can be interesting when you don't want to lose time
with moving enemies, like the servants before Moroes, where
the second tank already pulls the next enemy while the first
tank is still tanking.
If you want to use this feature the best option probably is
a pull macro like this:
/pullw force
/cast spellname

Known Issues
Attacks with cast time (eg. Aimed Shot, Fireball, Wrath) don't
seem to generate a combat log message containing the target until
after the character has officially entered combat. Due to this
a generic pull warning is displayed instead of the expected message
containing puller and target names.
Instant casts like Moonfire and Fearie Fire, or all ranged weapons
a warrior might use seem to work fine though.
Sometimes a warning is issued just after the enemy has died (it
seems to happen most commonly with the Curator). Since the addon
doesn't capture combat log events after the combat has ended,
I can only assume that combat events from other players arrive
a little late. But this happens so rarely that it is hard to
debug and probably only a very minor annoyance.

Changes Since Last Version

• Raid Warnings can now be optionally faked
• Spell Soothe no longer ignored, because it work differently now
• Checks if the target isn't a corpse to suppress some annoying warnings