Quote:
Originally Posted by Yinikren
[You must be logged in to view images. Log in or Register.]
This is a good idea, but honestly I don't know if they have any way of actually coding something like this.
And prepare for wow flames btw, I'm pretty sure something like this has been mentioned before.
|
It has. I saw it in the poll thread about disabling global /ooc (and /auction). Except the idea I saw was for continent-scale chat. I'm going for city-scale chat. The idea posted here in this poll is also self-imposed, not forced on the player. Those are the differences I can think but i bet someone somewhere has posted something exactly like this. If so, would love to hear from you.
I'm not against disabling global /ooc and /auction. In fact, I'd like to try it out to see how it works, but I think that this idea would be safer in the meantime. There might be technical limitations restricting something like this from working, but I'm not aware of them. I imagine they could add some code to the server for these options and could change the ui files to make them available to the client, but that is just a guess. It might not be possible - the client might not allow you to change it that way. For example, if the client hard code doesn't recognize the extra options, the changes to the ui file would be useless.
Only other choice is to make it a command. Like:
Code:
/globalchat filter:qeynos,erudin,halas
Global chat filter is set to: qeynos,erudin,halas.
-or-
Code:
/globalchat filter:kaladim,kelethin,akanon
Global chat filter is set to: kaladim,kelethin,akanon.
-or-
Code:
/globalchat filter:none
Global chat filter is disabled.
-or-
Code:
/globalchat
Global chat filter is set to: freeport.
I'm guessing that command strings like "/globalchat ..." are sent to the server without explicit client checks. For example, if you enter "/mcdonalds" it will tell you that the command is not available. My guess is that the server is receiving it and giving a negative response and the client is informing you.