New mute/blacklist options: a request

[Mawlzy]

It's gratifying to see SQEX provide more options for muting and blacklisting, but for Frontline players they have actually made matters worse.

Due to the presence of noisy commanders who feel the need to spam chat constantly, many of us used to blacklist them. This had the effect of completely removing their spam from chat. As far as I can tell, both the new mute and blacklist options broadcast that a message has been sent from a muted/blacklisted player.

The primary issue is that the original se.x that these people insist on sticking on their spam is still broadcast. The net result is far worse than the old system.

Could "mute" actually mean mute, such that nothing from muted players appears in chat or over sound?

[Mnemy]

Oh damn I didnt know the sound effect still plays when a muted/blacklisted character sends a message. Yeah it would be great if they remove the SFX. That shit could get annoying real fast.

[Mawlzy]

Oh damn I didnt know the sound effect still plays when a muted/blacklisted character sends a message. Yeah it would be great if they remove the SFX. That shit could get annoying real fast.

Could and does, yeah.

[RoanValorin]

I'm just curious, what are you frontlining for if you wont collaborate with someone that's trying to take direction?

the sound effects thing does seem like an annoying oversight though.

[Nyxs]

Yes please! Its the same as when you mute/blacklist people who do five lines macros to say hello/goodbye with a giant cat but you still get them but nows its just “sent from ___ user”. I dont want to see them at all if thats how they choose to talk. Its not cute. Its not funny. It’s annoying and spammy. I might also start muting people with raise macro thats are longer than a few words. {Raising} <t> or something similar is all that is needed.

[Rehayem]

Think it's been addressed in the patch notes.

[Nyxs]

Think it's been addressed in the patch notes.

Partially yes. It sounds like if you used a macro using <t> on them it appears as unknown instead of a name and now mutes sound effects which is a good fix but we also want the message gone completely also if they say anything. Maybe the next fix can include this.

[Mawlzy]

Partially yes. It sounds like if you used a macro using <t> on them it appears as unknown instead of a name and now mutes sound effects which is a good fix but we also want the message gone completely also if they say anything. Maybe the next fix can include this.

Agreed, this is much appreciated, but only half way there.

[Mawlzy]

I'm just curious, what are you frontlining for if you wont collaborate with someone that's trying to take direction?

the sound effects thing does seem like an annoying oversight though.

I enjoy communication and collaboration in FL. However, there are some commanders who spam chat macros and sfx to the point it is a distraction. Those I prefer to mute. Since they invariably also play DRK and lead a premade, it's trivial to follow them and target their target via macro. I can then provide better support than when sfx are exploding like someone shooting a xylophone with a machine gun.

[IvoryHawk]

It's gratifying to see SQEX provide more options for muting and blacklisting, but for Frontline players they have actually made matters worse.

Due to the presence of noisy commanders who feel the need to spam chat constantly, many of us used to blacklist them. This had the effect of completely removing their spam from chat. As far as I can tell, both the new mute and blacklist options broadcast that a message has been sent from a muted/blacklisted player.

The primary issue is that the original se.x that these people insist on sticking on their spam is still broadcast. The net result is far worse than the old system.

Could "mute" actually mean mute, such that nothing from muted players appears in chat or over sound?

Check at the bottom of todays patch notes, it's fixed now.