Repository navigation
Parse console log prefix on Bukkit servers - #190
Merged
Merged
Conversation
JulianVennen
approved these changes
Nov 13, 2026
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
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.
Bukkit servers write
[16:24:27] [Server thread/INFO]:tologs/latest.log, but[16:24:27 INFO]:to the console.Logs copied from the console were only parsed with the vanilla prefix, so no line matched and the whole log became a single entry starting at line 1, with the level of that first line.
Every problem in such a log pointed to that one entry.
This PR lets
BukkitLogmatch both prefixes in$patternand$prefixPattern.It is on
BukkitLogand not onVanillaLog, because the short console prefix comes from CraftBukkit and the servers based on it, not from vanilla.The level is still the second group, so the parser matches don't change.
Detection is not changed.
These logs are only detected as Paper because the unparenthesized
|inPaperLog::$logIdentifierletsThis server is running Paper versionmatch without any prefix.That is left for its own PR.
The expected output of all Paper 26.3 logs except
paper-circular-plugin-dependency-26-3.logchanged: they are now split into separate entries with their own levels.Their detected name, version, problems and information stay the same, only the entries the insights point to changed.
Changes
BukkitLog::$patternandBukkitLog::$prefixPattern