This site works best with JavaScript enabled. Please enable JavaScript to get the best experience from this site.
When summoning someone from a summoning stone, whether a default stone for a dungeon, or a warlock's conjured summoning stone, the act of sending a summons does not appear to be a UNIT_SPELLCAST_SENT, or any other event that is detected by SpeakinSpell. Please fix this.
I'll need to do some research to figure out if any notification exists for this in blizzard's API. There should be, and of course summoning is one of those ideal SpeakinSpell events you want to announce and whisper to your target, so this is important to make it work.
Grr @ Blizzard for not making this work with the UNIT_SPELLCAST_SENT event like most other actions.
3.2.0.06 adds combat event types: - (UNIT_SPELLCAST_CHANNEL_START) When I start channeling: ___ - (UNIT_SPELLCAST_CHANNEL_STOP) When I stop channeling: ___ - (UNIT_SPELLCAST_FAILED) When I fail to cast: ___ - (UNIT_SPELLCAST_INTERRUPTED) When I am interrupted when casting: ___ - (UNIT_SPELLCAST_STOP) When I stop casting: ___ - (UNIT_SPELLCAST_SUCCEEDED) When I succeed at casting: ___
I wonder if any of the new event types in 3.2.0.06 catch the summoning event?
increasing priority to high because summoning is such a perfect use for SpeakinSpell
I would like a related feature to announce when I receive a summons, for example to whisper to the summoner "/t <caster> I received your summon to <destination>, thank you" or tell the people around you where you're going "/s good bye everyone, I just got summoned to <destination><newline>/bye" (both of those examples would use an event-specific substitution data defined for <destination>)
3.2.0.06 added this 3.2.2.20 repairs <target> info in this event
The event is under Channeling Start/Stop "Summoning Stone Effect"
To post a comment, please login or register a new account.