Add %SERVER% formatter#28
Open
unique-nullptr wants to merge 2 commits into
Open
Conversation
okx-code
requested changes
May 21, 2026
okx-code
left a comment
okx-code
left a comment
There was a problem hiding this comment.
server is not part of the json payload for the various events
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Add %SERVER% formatter, so that events (skynet, snitch, chat, etc) can reliably be associated to the specific server which generated them.
This option is useful for allowing bots or users to identify which server a message came from, and so.
Without this option, it is impossible to reliably know which server a specific message originates from, without configuring the bot in some specific way (i.e: hard-coding a server identifier in the format string itself, OR keeping mini and main traffic to strictly separate channels and configuring/noting which is which manually). This is because multiple servers can theoretically have the same namelayer name, relayed to the same channel. This resolves that in an easy-to-use way.