Log Begone Wiki

Log Begone (mod id logbegone) is a small utility mod that removes unwanted lines from the game and server log. You list the messages you never want to see - as plain-text phrases or as regular expressions - in a single JSON config file, and every log line that matches is dropped before it is written: it never reaches the console window, the log file on disk, or the standard output stream.

Typical uses:

• Keep a dedicated server's console clean and readable by silencing repeated connection spam.
• Hide a chatty status message another installed mod prints over and over.
• Drop any specific line you never want in your log files again.

Log Begone is a standalone utility mod with no library dependencies, no commands and no in-game settings screen - everything is driven by its config file. The original mod is by AzureDoom (github.com/AzureDoom/Log-Begone), released under the LGPL-3.0 license.

Nothing needs to be crafted or configured in-game - Log Begone is pure configuration:

1. Run the game or server once with the mod installed. On first launch it creates logbegone.json in the instance's config folder, pre-filled with its default filters.
2. Spot a noisy line in your console or log file that you want gone.
3. Open config/logbegone.json in any text editor and add a distinctive part of that line to the phrases list (or a pattern to the regex list).
4. Start the game or server again. The filter list is read at startup - from then on, every line matching your entries is silently dropped.

The file is plain JSON, so entries can be added, edited or removed freely at any time; changes take effect on the next start.

All settings live in config/logbegone.json. The file contains a single logbegone object with two arrays:

Example structure:

{
  "logbegone": {
    "phrases": [
      "Disconnecting VANILLA connection attempt",
      "Channels "
    ],
    "regex": []
  }
}

Notes:

• phrases entries are simple and safe: no escaping needed, a plain copy-paste of part of the offending line is enough.
• regex entries must match the entire log line (Java String.matches semantics), so surround a fragment with .* - e.g. .*Unknown recipe category.* - to match lines containing it.
• The file is read once at startup; edit it, then restart the game or server to apply changes.

Log Begone ships with sensible defaults so it is useful out of the box. The generated logbegone.json pre-fills the filter lists with common connection-attempt noise:

• Disconnecting VANILLA connection attempt - the repeated message logged when a vanilla client or a server-list ping probes a modded server.
• Channels - the accompanying channel-negotiation line printed on such connection attempts.

These entries can be removed or replaced freely - they are ordinary list entries like any filter you add yourself.

Log Begone hooks the logging system itself at startup, which is what makes the filtering complete:

• It attaches its filter to the root logger and walks every other logger configuration it finds, attaching the same filter there, so messages from the game and from other installed mods are all covered.
• It also registers with the Java utility logging channel, catching libraries that log through that route instead.
• Finally it wraps the standard output stream, so even raw text printed directly to the console - outside any logging system - is checked against your filters.

Every candidate message is tested against the phrases list (substring match) and the regex list (full-line match). If anything matches, the line is discarded on the spot - it is not written to the console, not written to the log file, and not passed down the output stream. Non-matching lines pass through untouched.

Log Begone works on both clients and dedicated servers:

• On a dedicated server, install the mod on the server and edit the server's config/logbegone.json - the console and the server log files stay clean for every session. This is the mod's most popular use: server consoles accumulate repeated connection spam and status noise that the filter removes entirely.
• On a client, the same config filters your local game log.
• The mod only filters log output - it changes no gameplay behavior, so client and server installs are independent: it does not need to be present on both sides.

Does Log Begone add any commands or game rules? No. There are no commands and no in-game screen - all control is through config/logbegone.json.

Do I need any other mods? No - Log Begone is standalone with no library dependencies.

Do I have to restart after changing the config? Yes. The filter list is read at startup; edit the file, then restart the game or server for the changes to apply.

What is the difference between phrases and regex? phrases entries match if the log line merely contains the text; regex entries are Java regular expressions that must match the entire line (wrap fragments in .* to match anywhere).

Can it silence messages from other mods? Yes. The filter is attached to the root logger and to every logger configuration found at startup, plus the Java utility logging channel and the standard output stream - a matching line is dropped no matter which mod or library printed it.

Are the filtered lines saved anywhere? No. Matching lines are discarded before they are written - they appear neither in the console nor in the log files.

Will it hide errors I actually need? Only if your entries match them. Filters are exact: a line is dropped only when it contains one of your phrases or fully matches one of your regular expressions, so keep entries as specific as possible.

Does it work on servers? Yes - install it on the dedicated server and edit the server's config/logbegone.json; the console and log files are filtered for the whole session.