BlameLog
Every Minecraft player who has ever stared at a wall of console output knows the feeling. Something is spamming your log, your game is stuttering, and you have no idea which mod is responsible. BlameLog exists to answer that one burning question: who printed this line?
Created as a proof-of-concept mod and maintained under the tagline "Blaming logs since 2023," BlameLog patches Minecraft's logging system so that each message is prepended with the class and method that produced it. Instead of a vague INFO line, you get a clear pointer to the exact code responsible. It is a small utility, but for modpack authors and curious tinkerers it is genuinely transformative.
What BlameLog Actually Does
Under normal circumstances, Minecraft's log output tells you what happened but rarely who did it. A line like "Trying to read config file..." could come from any of the hundreds of mods in a modern pack. BlameLog rewrites that output so it reads something like [me.luligabi.noindium.NoIndium#createConfig] Trying to read config file.... Suddenly the mystery disappears.
The mod works by patching Loggers to prepend method callers, which means it hooks into the logging pipeline rather than modifying individual mods. That approach keeps it lightweight and broadly compatible, and it is exactly why the project is described as a proof of concept rather than a finished framework.
Supported Versions and Loaders
BlameLog is built for the Fabric loader and targets modern Minecraft releases in the 1.19 and 1.20 era, with builds published for several point versions across those cycles. If you run a Fabric-based instance on one of those versions, you are in the right place. Always check the file list on the project page to confirm the exact game version before you commit to a download.
Why You Would Want This
Log noise is more than an aesthetic problem. A mod that prints hundreds of lines per second can tank your framerate, bloat your latest.log into megabytes, and make crash reports unreadable. When you need to file a bug report or diagnose a conflict, a clean log is worth its weight in diamonds.
- Identify the exact mod behind spammy or repeated messages
- Speed up troubleshooting when two mods fight over the same feature
- Produce readable logs for bug reports and support threads
- Learn how your favorite mods are structured internally
- Spot misbehaving configs that quietly log errors every tick
If you have ever asked "which mod printed this?" while scrolling through pages of identical warnings, BlameLog was made for you.
Configuration and Patterns
Out of the box, BlameLog uses a sensible default pattern: [{simpleClass}#{method}] {message}. That gives you a compact class name, the method, and the original message. If you want more or less detail, the mod exposes a config file at config/blamelog-pattern.txt where you can define your own format.
Available Pattern Tokens
- class — inserts the full class name, package included
- simpleClass — inserts just the class name without the package
- method — inserts the method name that triggered the log
- methodParams — inserts the parameters passed to that method
- methodReturnType — inserts the return type of the method
For deep debugging sessions, combining class, methodParams, and methodReturnType gives you an almost stack-trace level of context without the overhead of an actual exception. For everyday use, the default pattern keeps things tidy.
How to Install BlameLog
Getting started is straightforward. First, confirm that you are running a Fabric profile on a supported Minecraft version. Next, make sure the Fabric API is present, since most Fabric utilities depend on it. Then place the BlameLog jar file into your mods folder alongside your other add-ons.
If you would rather skip the manual file juggling, the foxygame.net launcher handles the whole process in a single click and keeps BlameLog updated automatically whenever a new build lands, so your logs stay readable without you lifting a finger. Launch the game once to generate the default pattern file, tweak config/blamelog-pattern.txt if you want a custom format, and you are done. From that point on, every log line carries its own origin story.
A Small Mod With a Big Payoff
BlameLog is not the kind of mod that adds biomes, bosses, or shiny new gear. It is a diagnostic tool, and it excels at the narrow job it was designed for. When your pack misbehaves, when a log file balloons out of control, or when you simply want to know which mod is responsible for that suspicious warning, BlameLog hands you the answer on a silver platter. Download BlameLog, drop it in your mods folder, and never wonder who printed that line again.