#RAID ALERT ISSUES UPDATE#

This may be a similar question to #1521, where you disagree with what's considered safe or not here. It would be helpful to have a log with a specific pull time that did something wrong. I think if you have a pull where something appears different than the above list, or worse that somebody is told to go a direction that doesn't correspond to what the directions are, please let me know. I took a look through the network log that was sent and didn't see anything that looked wrong to me. There's more time to wait for the first dive and place it north, imo. SW is less safe, because there's less time between mark placement and dive. You have two options, you can put mark 3 SW (in front of dragon 2) or N. The second dragon is SW so you put mark 2 south. The first two dragons are NE and E, so you put mark 1 north. : (wide)Ĭactbot will never say 'NE, SE, NE' as mentioned above, but there are cases where the 1st and 3rdmark are the same. Triage notifications on the go with GitHub Mobile for iOS or Android. Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned. The active alert list, the alert history. The RAID log focuses on four key areas: Risks events that can have an adverse impact. Typically, alerts that require user intervention will turn on the Information LED on the SAS RAID controller module. This helps keep the conversations flowing.

#RAID ALERT ISSUES UPDATE#

The team can easily refer to it in project audits and update meetings. Is that not true? Do you want to move this conversation there if these suggestions don't work? A RAID log template lets you continuously record project risks, assumptions, issues and dependencies over a period of time in an organized way.

Finally, you filed but closed #3417, which made me think that you had fixed it. You should also take a look at #2727, #2830, and #3358 for people who have had similar problems because of settings.

You could verify this is the problem by looking in your log and seeing if you see the nael dialog lines. The most likely problem for you is that you have 'Hide chat log for privacy' clicked or you have not enabled NPC dialog to show up in game (and thus it won't make it to the log). To: quisquous/cactbot MrTefty Mention Re: Ucob raid alert wrong info ( Thanks, I'll take a Nael RP quotes sound like a separate issue than this. That was driving me insane for ages and also explains why none of my custom triggers would work for Nael either…įrom: Adrienne Walker 17 October 2021 16:41 Might be worth shoving in a comment somewhere under the Ucob section or at the top of the raid boss area stating that this might needs turning off for some alerts to work as it appears to be on by default. You sir are a legend, it was simply the “Hide Chat Log (for privacy)” option.

Raid alert issues