
Ember's Log Filtering
A highly configurable log filtering mod for Minecraft
About this Mod
LogFilter
A highly configurable log filtering mod for Minecraft. Suppress noisy log messages, highlight important ones, and keep your console clean — all with hot-reloadable rules.
Features
- Regex message filtering — Match and suppress log messages by content using regular expressions
- Logger name filtering — Filter by exact logger name or regex pattern, with hierarchical matching
- Log level filtering — Target specific log levels (DEBUG, INFO, WARN, ERROR)
- Filter actions — DENY (suppress), ALLOW (force show), or NEUTRAL (pass through) per rule
- Per-rule enable/disable — Toggle individual rules without removing them
- Hot-reload — Edit
logfilter.jsonand changes apply instantly, no restart needed - Default rules included — Ships with pre-made (disabled) rules for common log spam
Supported Platforms
| Loader | Minecraft Version |
|---|---|
| Forge | 1.20.1 |
| NeoForge | 1.21.1 |
| Fabric | 1.20.1 |
| Fabric | 1.21.1 |
Configuration
LogFilter stores its config in logfilter.json in your Minecraft config directory. The file is created automatically on first launch with sensible defaults.
Example Config
{
"configVersion": 1,
"enabled": true,
"rules": [
{
"name": "Suppress OpenAL spam",
"enabled": true,
"type": "MESSAGE_REGEX",
"pattern": "(?i)openal",
"action": "DENY",
"level": null
},
{
"name": "Block debug logs from server level",
"enabled": true,
"type": "LOGGER_NAME",
"pattern": "net.minecraft.server.level",
"action": "DENY",
"level": "DEBUG"
},
{
"name": "Always show errors",
"enabled": true,
"type": "LEVEL",
"pattern": "ERROR",
"action": "ALLOW",
"level": null
}
]
}
Rule Types
| Type | Description |
|---|---|
MESSAGE_REGEX |
Match the log message content against a regex pattern |
LOGGER_NAME |
Match by exact logger name or prefix (hierarchical) |
LOGGER_REGEX |
Match logger names using a regex pattern |
LEVEL |
Match by log level (DEBUG, INFO, WARN, ERROR) |
Actions
| Action | Description |
|---|---|
DENY |
Suppress the log message |
ALLOW |
Force the message through, regardless of other rules |
NEUTRAL |
No effect — pass through to the next rule |
Optional Level Restriction
Any rule can include a level field to restrict it to a specific log level. For example, a LOGGER_NAME rule with "level": "DEBUG" will only match debug messages from that logger.
Default Rules
LogFilter ships with several pre-configured rules (disabled by default) to get you started:
- Suppress OpenAL/LWJGL info spam
- Suppress advancement loading messages
- Suppress debug logs from
net.minecraft.server.level - Suppress recipe loading messages
- Always allow ERROR-level messages
Enable them by setting "enabled": true in the config file.
Available Versions
How to Install Ember's Log Filtering 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 "Ember's Log Filtering". Click "Install" – done! Alternatively, upload the .jar via SFTP to the /mods folder.
Compatibility
Mod Loaders
Minecraft Versions
1.21.1, 1.20.1
Server-side
✗ UnsupportedRecommended RAM
4 GB(min. 3 GB)Frequently Asked Questions
Ember's Log Filtering 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 Ember's Log Filtering compatible with fabric and forge and neoforge?
Ember's Log Filtering officially supports fabric, forge, neoforge for Minecraft 1.21.1, 1.20.1. 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 Ember's Log Filtering – how to optimize performance?
Recommended RAM: 4 GB (per 8 players). Use /spark profiler to check if Ember's Log Filtering 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 Ember's Log Filtering with just one click on your server.