SpeakinSpell

145 - Guild Achievements earned by the whole guild

What is the enhancement in mind? How should it look and feel?

(SS 4.0.3.05) Guild Achievements are currently identified the same as a guild member getting an achievement, and <caster> comes out as <guild> ... but it should really be a separate event trigger which can have its own speech list, because this is a special different case from an individual getting an achievement.

Please provide any additional information below.

It's the same Blizzard API event hook that we're already using.  Just check for <caster>==<guild> and change the event key.  This wants some new content to go with it too - new speeches to grats the guild as a whole.

User When Change
rismisner Jan 16, 2013 at 20:05 UTC Changed assigned to from rismisner to Duerma
rismisner Dec 24, 2010 at 21:55 UTC Changed priority from Medium to High
rismisner Dec 20, 2010 at 20:18 UTC Create

You must login to post a comment. Don't have an account? Register to get one!

  • 4 comments
  • Avatar of rismisner rismisner Jan 16, 2013 at 20:05 UTC - 0 likes

    I'm re-assigning all my tickets to Duerma

  • Avatar of rismisner rismisner Jul 25, 2011 at 22:50 UTC - 0 likes

    Guild achievements broke in 4.1. I assume they come through the API as a new independent event now.

  • Avatar of Aetharan Aetharan Feb 25, 2011 at 07:40 UTC - 0 likes

    It's issues like this that actually make me wish there was an easy if/then/else syntax I could use in the redirect macros, as the workaround logic for things such as this would be amazingly simple:

    if <caster> = <guild>
    then /ss macro gratsguild
    else /ss macro gratsdude

    Or, perhaps, a way to create a "wildcard" for any unspecified value, so that I could create /ss macro grats<guild> and /ss macro grats"wildcard", so that if my one speech on an achievement being printed in /g is "/ss macro grats<caster>" and <caster> comes out guild, it goes to that one, but anything else will call the wildcard macro instead.

  • Avatar of rismisner rismisner Dec 24, 2010 at 21:55 UTC - 0 likes

    Increased the priority on cataclysm-related updates

  • 4 comments

Facts

Last updated
Jan 16, 2013
Reported
Dec 20, 2010
Status
Accepted - Problem reproduced / Need acknowledged.
Type
Enhancement - A change which is intended to better the project in some way
Priority
High - Strongly want to resolve in the specified milestone.
Votes
0
Component
Event Hooks

Reported by

Possible assignees