Forward server and tunnel output with source prefixes - #30
Open
afrigon wants to merge 15 commits into
Open
Conversation
- log4j console pattern prefixes lines with MINECRAFT [LEVEL] [thread] - server output is always read; join and leave events print status lines - tunnel agent output is echoed with a TUNNEL: prefix under --tunnel-logs
- Minecraft lines carry a level-colored dot, tunnel lines the provider label - autosave completion prints the time since the save started
- the log4j console appender never drops below info so events are always seen - echoed lines and events are filtered against mc's own log level
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
1 participant
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.
First pass on #12: the server console is always read by mc, and player join and leave events are printed as status lines whether or not
--server-logsis passed.log4j2.xmlconsole pattern becomesMINECRAFT [LEVEL] [thread]: message; the file appender keeps the standard pattern--server-logseach line is echoed to stdout ahead of any status line it produced--tunnel-logspipes the agent and echoes every line asTUNNEL: ...; without the flag the agent keeps logging to.tunnel/playitd.logminecraft/log.rswith tests for the join and leave shapes and for player-controlled text that must not matchRefused-login events and the notifier toggle from the issue are left for a follow-up.