Guild Wars 2

For the past few hours I’ve been saying (among other things) the following in [Team] chat every 20-25 minutes: “siege refreshed at hills”.

now I’m getting a message saying “Your message was suppressed due to excessive messaging.” how can I get rid of this? how can I prevent it from coming back?

-ken

Change a letter

You need other people to be also using Team chat. The more of you without anyone else in any channel, the longer and more likely you are to be suppressed.

Peetee.9406:

Change a letter

^ This.

As a commander, I can shout all kinds of thing in rapid succession. I rely on pick-ups a lot, so I also type a lot. For all the talking I do, I’ve only been suppressed once. It seems the suppression is designed to target people who repeat themselves (such as bots, or those spamming guild recruits).

The workaround (albeit a lame one) is that commanders are never suppressed in Squad Chat. Whether or not I’m flying my pin, I personally never use squads. As a commander I can’t rely on the fact that my followers joined my squad, because there’s a good chance they didn’t. As a follower, I never join squads because I want to know where all the commanders on the map are (once you join a squad, you can’t see other pins).

The response from a mod was, “use squad chat”.

You cant always use squad chat..not everyone is in your squad,sometimes people need to see the textbubble for them to get your attention,so switching to /say is a Must at alot of occasions.They just have to fix this and lower the possibility to be supressed for commanders.

Hey, I’m just the messenger. Squad chat wouldn’t be so bad if it didn’t mean only being able to see one commander’s icon. Either way that’s their response to the whole suppression issue, so I guess they won’t look into it any further.

thanks for the answers.

this was during a very quiet time in the zone so there were relatively few of us, and my status updates ended up being a significant fraction of the activity in /team. I’ll try to vary my text a bit to avoid this in the future.

(and in case anyone is wondering, relogging does not clear this, I had to wait it out)

-ken