Any option is likely better than we have at the moment lol And your idea is a good one. I think what I would do, server side, is have a list. Every player is on the “Shout” list by default, but when a player ticks the option to disable shout what they actually do is send an update to the server saying to remove their name from that list. When they enable shouts again they actually send an update to the server to be put back on the list.
Right now when we get a shout the server has to send the packets to every client online so sending only to a list sounds like it would take another step but it would actually take a little load off the server instead and the client wouldn’t receive the packets that way.
But I think it’s great that we can come up with possible solutions to help. If we can get enough attention maybe IMC will even pick up one of the ideas so the more the merrier.
I’ve seen Staff tagged in recent messages about silly little things though and they jump in the thread without hesitation and leave a reply. Bring up something important and they intentionally go silent. I’m hoping we can make it so they realize that if they choose to reply to any threads at all then it should be for real issues instead of spending their time in the forums replying to threads about one single person having trouble with a certain quest or an item not giving the full attack it should etc. We have a game full of past exploiters, current hackers, everyone and their mom being affected by FPS issues in GvGs and world bosses, and bugs and exploits that are still going on (Thaum transpose exploit, CC bugs in TBL/GvG via Snow Rolling and other skills, GvGs and TBL being crashed intentionally and accidentally, etc etc). These are the messages that demand attention. These are the messages that need replies. Not a Staff reply to an individual because that person misread an event or whatever.