Instead of having to do the constant /join ### to switch channels, could we get a more streamlined system where we use /join ### to listen, and /### to send a message to that channel?

If they try to do /### and they haven't joined the channel, either spit out an error telling them they must join the channel, or autojoin them on send.

Finally, keep track of the last /### so that players don't have to use this convention on successive messages to the same channel. (i.e. would message 100 thereafter the first usage of /100 until another channel is messaged instead.)

So...you want to change /join X to /X?

If anything, /X shouldn't change the channel you are joined in the rare case you want to send one quick message to channel X.

But overall, this is on the other side of the universe from 'necessary,' so it's way low on the priority list.

"join" wouldn't actually leave the current channel, only push it to the background (dark blue text) like the current system. On the off chance, you send a message to /11 then want to speak again on 100 afterwards, you would simply /100. Perhaps /### with no message should set that channel to the foreground again, so it will default on the next message.

Or allow something akin to /join *### (exp. /join *100) where the * specifies that channel to be the default send-to channel on send without a slash specifier. Maybe even a simple UI option, in the escape menu along side the hail message to specify the default channel.

I'd ratter have a tab-like structure for joined-up channels with the option of keeping some channels on same tab (like what's currently done).

Aka,

/join would keep doing what it does
/open nn would create a new tab for channel nn next to the General/Mission tabs (with cycling with F2)
/nn would send message to channel nn and /join it in current tab if not /open already
/close nn would close channel tab nn

It'd be nice for the new UI to have a graphical comm pad pop-up to manage channels.