Closed YuzukiTsuru closed 3 weeks ago
@YuzukiTsuru Thanks for your contribution! 🌵🚀
I think this would display an alert each time the user is hit, so if they are hit 3 times, that would be three back-to-back alerts. That feels a little noisy to me, especially since the hits occur immediately in succession (meaning stale alerts will continue to be displayed after a subsequent hit).
As an alternative, I'd suggest displaying only the total hit count (perhaps combined with 'Short' or 'Long') after all hits have happened, and I think just as an infoText
(since the info doesn't require immediate action until the next mechanic, which has its own alert).
That still may be a little noisy for short-debuff players, who then will shortly thereafter get a Spread (x stacks)
call -- but I think that's probably better than repeated alerts as the hits are happening.
(Feel free to disagree - just my $0.02.)
I think this would display an alert each time the user is hit, so if they are hit 3 times, that would be three back-to-back alerts. That feels a little noisy to me, especially since the hits occur immediately in succession (meaning stale alerts will continue to be displayed after a subsequent hit).
As an alternative, I'd suggest displaying only the total hit count (perhaps combined with 'Short' or 'Long') after all hits have happened, and I think just as an
infoText
(since the info doesn't require immediate action until the next mechanic, which has its own alert).That still may be a little noisy for short-debuff players, who then will shortly thereafter get a
Spread (x stacks)
call -- but I think that's probably better than repeated alerts as the hits are happening.(Feel free to disagree - just my $0.02.)
Well, because it's easy to count hits that don't belong to you, it's designed to show you every hit. I'll change to infoText
Well, because it's easy to count hits that don't belong to you, it's designed to show you every hit. I'll change to
infoText
Sorry, but I still think this is too noisy. For example:
Because these triggers stay active for four seconds, the infoText alerts simply stack on top of one another (scrolling the oldest off). With the default sound effect from each one, it also adds a lot of auditory clutter.
Since the actual hit count isn't needed until later, I'm not sure I see the rationale for firing an alert for each hit, as opposed to just displaying the total count once the hits are finished. And even that has potential to be unnecessarily noisy for short-debuff players, given this:
If you wanted to add a single infoText
trigger that displays total hit count just for long debuff players once the hits have finished (e.g. 3 stacks (later)
), I think that's fine though.
That makes sense. Let me fix it
add R4S Witchgleam Self Tracker reminder
Simply show each witchgleam you got