This repository has been archived by the owner on Sep 12, 2021. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
About The Pull Request
The AI Private Channel token :o had stopped working, because the Borer Channel token was also set to :o and it took precedence over the AI Private Channel. I resolved this issue by changing the Borer Channel to :j.
There doesn't appear to be a single list with all the tokens in it. At the time of writing, it appears that :f, :j, :q, :w, and :z are still available. I believe :1 - :9 and :0 are also still available. It seems that the way to tell is to try to send a message on the channel, and if it returns the token, it's free. The example being if you say "test" using ":z", it'll say ":z test" back to you.
It also occurs to me that this can easily break if upstream decides to use :j for something else and we don't notice.
Channel output examples:
Headset using :o test
AI using :o test
Borer using :j test
Why It's Good For The Game
Bug fix: Issue #466
Changelog
馃啈
fix: AI channel :o works again
tweak: Borer channel changed from :o to :j
/:cl: