
Log Filter
Filters configured messages from the log and console in a performant way.
About this Mod
Log Filter
Filters configured messages from the log and console in a performant way.
This is intended to be used by pack creators. Consider NOT send modified logs to mod creators if you're reporting bugs.
Usage
Below is a commented config file ("log_filter.json") to remove all logging of datapack loading failure. This can be useful if a datapack removes recipes by e.g. replacing them with empty files. To use this, you need to remove the comments!
{
"logEvents": "NONE", //Setting this to "INFO" will change ALL messages logged into a format useful to configure this mod (see below)
"rules": [ // Array of rules. If a rule matches, the message will not be logged
{
"level": [ // Array of levels. These are combined by AND within a rule.
{
"relation": "EQUAL", // Relation (Supports EQUAL, NOT_EQUAL, GREATER_THAN, etc.)
"value": "ERROR" // Value must be a valid level
}
],
"loggerName": [ // Array of logger names
{
"relation": "MATCH", // Relation
"value": "net.minecraft.server.packs.resources.SimpleJsonResourceReloadListener" // Class
}
],
"formatMessage": [ // The message with formatting not applied (with the placeholders instead of values)
{
"relation": "MATCH",
"value": "Couldn't parse data file {} from {}"
}
],
"parameterClasses": [ // Types of parameters/placeholders
{
"0": { // First placeholder
"relation": "MATCH",
"value": "net.minecraft.resources.ResourceLocation"
},
"1": { // Second placeholder
"relation": "MATCH",
"value": "net.minecraft.resources.ResourceLocation"
},
"2": { // Etc.
"relation": "MATCH",
"value": "com.google.gson.JsonParseException"
}
}
]
}
]
}
If "logEvents" is set, all log messages will be transformed:
[20:18:10] [modloading-worker-0/INFO] [Log Filter/]: Logging event:
- Level: INFO
- Logger name: mezz.jei.library.load.PluginCaller
- Thread name: modloading-worker-0
- Throwable class: null
- Message: Sending ConfigManager...
- Format message: {}...
- Parameter classes: [java.lang.String]
Available Versions
How to Install Log Filter on Your Server
Order Server
Order a Minecraft Java server with at least 3 GB RAM (4 GB recommended).
Set fabric Loader
In the panel under "Egg", select the fabric loader and matching Minecraft version (1.21.1).
Install Mod
Open the mod browser in the dashboard and search for "Log Filter". Click "Install" – done! Alternatively, upload the .jar via SFTP to the /mods folder.
Compatibility
Mod Loaders
Minecraft Versions
1.21.1, 1.21
Server-side
~ OptionalRecommended RAM
4 GB(min. 3 GB)Frequently Asked Questions
Log Filter server crashes on startup – what to do?
Most common cause: wrong fabric version or insufficient RAM. Check the server log (latest.log) for "OutOfMemoryError" or "Mixin" errors. With Mado Hosting: ensure at least 3 GB RAM is allocated and the loader matches the mod version (1.21.1). You can switch loaders with one click in the panel.
Is Log Filter compatible with fabric and forge and neoforge?
Log Filter officially supports fabric, forge, neoforge for Minecraft 1.21.1, 1.21. Note: Forge and Fabric mods are NOT cross-compatible – pick one loader and stick with it. The Mado dashboard automatically detects incompatible loader combinations.
Server lagging with Log Filter – how to optimize performance?
Recommended RAM: 4 GB (per 8 players). Use /spark profiler to check if Log Filter consumes the most tick time. Common fixes: reduce server view-distance to 8-10, install "performant" or "starlight" as supplementary mods on Forge. With Mado Hosting, your server runs on NVMe SSDs with dedicated CPU cores for minimal latency.
Similar Mods
Rent Modded Server
Install Log Filter with just one click on your server.