GemSay

*** 1.8 ***
2010 Oct 16:
        * Updated GemSay for WoW 4.0.1.
        * Replaced the deprecated "this" keyword with "self".
2009 Nov 1:
    * Modified the emote change just slightly: if there is an emote in
    the message and if there is an argument after it (any argument at
    all), then GemSay will tell WoW to pay attention to whether you
    have a target selected when issuing the emote.  If there's no
    argument, GemSay will tell WoW to ignore whatever target you may
    have selected and issue the emote as if you have no target
    selected.  In other words, "/gs y /laugh xyz" will do "You laugh
    at <target name>." if you have a target selected and "You laugh."
    if you have no target; "/gs y /laugh" will always do "You laugh."
    whether you have a target selected or not.  You can't customize
    the text that appears when the emote happens; that's a limitation
    imposed by WoW (but on the other hand, the fact that the text is
    standard means that opposite-faction players can read it too).
    * I have merged Yltseirp of Cairne's suggestion and Renvan's first
    suggestion into one unified system.  Now when the outgoing message
    begins with a /, GemSay will first see if it's a chat command and
    act accordingly, then see if it's an emote command and act
    accordingly, in both cases going through Blizzard's global
    variables so there's no need for me to keep huge lists of all the
    emotes or all the abbreviations for chat commands.  This means
    that the destination-overriding possibilities from v1.7 are still
    there but slightly improved (every abbreviation allowed by WoW is
    allowed by GemSay too, like /g, /gc and /gu for /guild), *plus*
    you can have your character do any of the standard emotes as the
    outgoing message.  A side effect is that anything after an emote
    is ignored, and of course you can't broadcast an emote to any chat
    mode other than EMOTE, so "/gs y /laugh bob" works the same as
    "/laugh" with no target selected: "You laugh."  (Note that the
    destination code "y" is completely ignored because of the emote,
    as is the "bob" that comes after it.)  You will do the animation
    and sound, however, and the emote will be readable by the opposing
    faction.
    * Still frustrated about what event (if any) is generated if you
    sit on a chair/bench, right-click on a feast, right-click on a
    portal to participate in a ritual (like a meeting stone or warlock
    summon, a mage table summoning spell, a warlock soulwell, etc.).
    This is annoying me because I'd like to say something when I do
    this, but so far I'm coming up empty.  It seems to me as if no
    event whatsoever goes out when you do these things.  You can,
    however, set a trigger for when you *start* a summon using a
    meeting stone or warlock summoning portal, just not when you
    assist in creating the warlock summoning portal or in summoning
    somebody with it.
    
2009 Oct 31:
    * Sending a message to destination "o" (guild officer chat) can
    now check to see whether you have permission to do that.  This
    means that destination paths like "ogrps" would work (try guild
    officer chat first, then guild chat, etc.).
    
2009 Oct 24:
    * Added triggers for other types of spell/ability misses besides
    RESIST -- ABSORB, BLOCK, DEFLECT, DODGE, EVADE, IMMUNE, MISS,
    PARRY, and REFLECT.  This is Renvan's second suggestion.
    * Fixed a bug when you hit Cancel while creating a trigger, then
    hit New Trigger -- it used to retain data from your canceled
    trigger.  Now it doesn't.
    * Widened the trigger name box so you can see the whole event and
    spell it triggers on.
    
2009 Oct 23:
    * Added UNIT_SPELLCAST_CHANNEL_START to the capture -- apparently
    things like summoning portals trigger this without triggering SENT
    or START.
    * Changed event handling code to still trigger on a CHANNEL_START
    that arrives without a SENT.
    * Still can't find what event, if any, fires when you sit on a
    chair or right-click on a feast.  Might it be PLAYER_CAMPING?
    (Answer: No.)

2009 Oct 22:
    * Fixed a bug when printing certain error messages -- they
    attempted to call the message() function improperly, leading to
    Lua errors.
    * Fixed a bug: the button onto which to drag spells or items when
    creating a trigger no longer toggles its border bright or dark
    when clicked.
    * Added the "Capture Next Cast" button in the spell panes of the
    trigger editor window.  A new way to enter spells that can also
    capture a right-click on a world object!  This can only trigger on
    "Cast Button Pressed" (a.k.a. UNIT_SPELLCAST_SENT) events, though.
    Unfortunately it only works so far on objects that actually show a
    cast bar, like opening chests.  I have not figured out how to make
    this work for instant-cast channeled objects like the portals that
    appear when mages cast Ritual of Refreshment or warlocks cast
    Ritual of Summoning/Souls/Doom, or the portals that appear when
    somebody uses a meeting stone or warlock summoning portal.