107 - Chat spam about "announcement" conflicts. Then announces don't happen.
What steps will reproduce the problem?
1. Have yourself as an assistant in the raid Join a raid with someone else using the same EnsidiaFails version (who is not an assistant). 2. Have your "announcement" settings set to only notify you of failures in the chat1 frame after a boss fight.
What is the expected output? What do you see instead?
Expected: same behavior as previously: I will receive the announcements of fails in the chat1 frame after the fight. Instead: I get spammed before the boss fight: "(player) has priority on announces. (Player) has the same EnsidiaFails version as you. Your announces will be disabled" (or similar, going by memory). A few seconds later: "You have priority on announces. (Player) has the same EnsidiaFails version as you. (Player's) announces will be disabled." (or similar). It continues this spam until the fight starts.
Then after the fight, I never receive notifications of who failed what (and yes, people did fail).
What version of the product are you using?
v3.2 (release)
Please provide any additional information below.
Totally unacceptable behavior. It should never auto-disable your own announces, whether being output to yourself in chat or to the raid.
| User | When | Change |
|---|---|---|
| Zidomo | Tue, 03 Nov 2009 19:09:33 | Changed status from Waiting to Replied |
| mysticalos | Tue, 03 Nov 2009 01:32:19 | Changed status from Replied to Waiting |
| mysticalos | Mon, 02 Nov 2009 06:03:04 | Changed status from Waiting to Replied |
| Maat | Fri, 30 Oct 2009 21:44:54 | Changed status from New to Waiting |
| Zidomo | Fri, 30 Oct 2009 16:37:15 | Create |
- 4 comments
- 4 comments
Facts
- Last updated on
- 03 Nov 2009
- Reported on
- 30 Oct 2009
- Status
- Replied - Someone has replied after waiting for more information.
- Type
- Defect - A shortcoming, fault, or imperfection
- Priority
- Medium - Normal priority.
Reported by
Possible assignees
-
- Manager
- Author
-
- Author
- #4
mysticalos Wed, 04 Nov 2009 18:44:07yeah disable announce override works, But typically all raid members will have to do this cause if they don't disable theirs, theirs may still think it's supposed to announce based on what last override command was sent by yours before disabling.
- #3
Zidomo Tue, 03 Nov 2009 19:09:32Instance: Onyxia's Lair (before the fight). Version was as noted in the ticket above: v3.2 (release).
Yes, the behavior occurred as noted by Mysticalos below: entering the instance. Still, whether or not EnsidiaFails decides to make you the "lead announcer" or not, it again should never (ever) stop fail announcing to yourself/guild/officer chat (as opposed to raid chat).
There is an option I overlooked, though: "Disable announce override". If this behaves as noted- -"Disallows accepting commands from other users that'd change the announcing settings"- -and prevents other users from shutting off your fail notifications, fine. If it doesn't work like that, it needs to be changed. ASAP ;).
Since the alphas using LibFail-1.0 have been out for a while, now moving on to them. Will see what happens.
- #2
mysticalos Mon, 02 Nov 2009 06:03:03i do know you'll see the messages often if you and others are zoning. It will always set whoevers inside the instance to announcer, so after a wipe it may switch back and forth while people are zoning in and out.
- #1
Maat Fri, 30 Oct 2009 21:44:44which fight did this happen on? What version were you using?