Ember's Log Filtering in Project Infinity 0.1

Ember's Log Filtering (LogFilter) is a utility mod that cleans up your Minecraft console. It lets you suppress noisy log messages, force important ones to show, and keep the log readable. This pack includes version 1.1.2, the Forge 1.20.1 build.^[1][2]

Everything is controlled by rules in a single file, logfilter.json, in your Minecraft config folder. The file is created automatically on first launch.^[1]

How rules work

Each rule has a type that decides what it matches:^[1]

• MESSAGE_REGEX matches the log message content against a regular expression.^[1]
• LOGGER_NAME matches an exact logger name or a prefix, so it works hierarchically.^[1]
• LOGGER_REGEX matches logger names with a regular expression.^[1]
• LEVEL matches a log level: DEBUG, INFO, WARN or ERROR.^[1]

Each rule also has an action. DENY suppresses the message, ALLOW forces it through regardless of other rules, and NEUTRAL has no effect and passes the message to the next rule. Any rule can also carry a level field to restrict it to one log level, for example a LOGGER_NAME rule that only catches DEBUG messages from one logger.^[1]

You can switch individual rules on or off without deleting them. Edits to logfilter.json are hot-reloaded, so changes apply instantly with no restart.^[1]

Default rules

The mod ships with pre-made rules for common log spam: OpenAL/LWJGL info spam, advancement loading messages, debug logs from net.minecraft.server.level, recipe loading messages, and a rule that always allows ERROR-level messages.^[1]

Good news first: there is nothing to craft here. This mod is a log filter, so it doesn't add a machine or tool to build. Everything happens in one config file, and the pack has already filled it in for you.^[1]

Unverified No in-pack recipes or quests for this mod were found in the available sources, so there is no recipe to show and no quest chapter to follow.

What the pack already does

The mod suppresses noisy log messages so your console stays readable. In this pack the filter is switched on, and the config sets enabled to true. The file format version is set by configVersion, which is 1 here.^[1][3]

The mod's own defaults ship disabled, but this pack goes further. Its rules list is a long set of rules, each named "Suppress", with the action set to DENY and the rule enabled. They hide known harmless spam, such as missing-texture warnings, recipe parsing complaints and mixin noise.^[1][3]

Your first steps

1. Open config/logfilter.json in your Minecraft config folder. The mod creates it on first launch, and the pack ships its own version.^[1][3]
2. Check that enabled is true. If you ever want to see the raw, unfiltered log, this is the master switch.^[1][3]
3. Skim rules to see what is hidden. Most entries use the MESSAGE_REGEX type, which matches the message text, or the LOGGER_REGEX type, which matches the logger name.^[1][3]
4. Look for the optional level field. Some pack rules only apply at one level, for example WARN or ERROR, so they hide a message only at that level.^[1][3]
5. Save the file. The mod hot-reloads, so edits apply straight away and you don't need to restart the game.^[1]

Changing a rule

If a message you need is being hidden, set that rule's enabled value to false. This keeps the rule in the file so you can switch it back on later. You can also use the ALLOW action, which forces a message through regardless of other rules. NEUTRAL passes a message on to the next rule.^[1]

This one is a bit different from the machine mods you're used to. The sources describe it purely as a log filter, so there are no machines to build or feed. It looks at each message the game writes to the log and decides whether to show it or hide it, based on rules you define in a JSON file.^[1]

How a rule works

Each rule has a name, an enabled switch, a type, a pattern, an action and an optional level. The type decides what the pattern is compared against, and the action decides what happens to a matching message.^[1]

• MESSAGE_REGEX matches the content of the log message against a regular expression.^[1]
• LOGGER_NAME matches an exact logger name or a prefix of it (hierarchical matching).^[1]
• LOGGER_REGEX matches logger names using a regular expression.^[1]
• LEVEL matches by log level: DEBUG, INFO, WARN or ERROR.^[1]

The actions are DENY, ALLOW and NEUTRAL. DENY suppresses the message. ALLOW forces it through regardless of other rules. NEUTRAL does nothing and passes the message on to the next rule.^[1]

Any rule can also carry a level field that restricts it to one log level. For example, a LOGGER_NAME rule with the level set to DEBUG only matches debug messages from that logger.^[1]

What this pack does with it

The pack's config lives in config/logfilter.json. The mod's own pre-made rules for common spam are disabled by default, but in this pack the master switch enabled is set to true. The file also has a version marker, configVersion, set to 1.^[1][3]

Everything lives in rules. Every rule in the pack's list is enabled, every one uses the DENY action, and every one is named Suppress. In other words, the pack uses the mod only to hide noise, and it never uses ALLOW or NEUTRAL.^[3]

The pack only uses two rule types: MESSAGE_REGEX and LOGGER_REGEX. Most rules match message text, such as load warnings about recipes, tags, models and textures. Others match the logger name instead, for example the Mixin locals utility and a few classes from other mods in the pack.^[3]

Level-restricted rules

Some of the pack's rules use the optional level restriction so they only hide a certain severity. The message pattern Texture is only denied at WARN level, and the logger pattern net.minecraft.ResourceLocationException is only denied at ERROR level. Another rule hides messages matching Hiding only at INFO level.^[1][3]

Ember's Log Filtering keeps everything in one file, config/logfilter.json. There are only a few top-level options, and nearly all the action is in the rules list. The mod page says you can edit the file and changes apply instantly, with no restart needed.^[1][3]

The options

• configVersion is 1 in this pack.^[3]
• enabled is true in this pack, so filtering is switched on.^[3]
• rules is where the pack does its work. It is a long list of rules, each with a name, a type, an action, an enabled flag and a pattern.^[3]

What the pack changed from the mod's defaults

The mod page says it ships with pre-made rules for common log spam, and that those rules start out disabled. This pack goes the other way: it supplies its own rules, and they are set to enabled. Every rule uses the DENY action, which suppresses the matching log line.^[1][3]

The pack uses two rule types, MESSAGE_REGEX and LOGGER_REGEX. The first matches the text of a log message. The second matches the logger that wrote it. Some rules also set a level, so they only apply to messages at that level (WARN, ERROR or INFO).^[1][3]

What the pack hides

The rules are all named "Suppress". Some examples of what they target:^[3]

• Model and texture complaints, such as "Failed to load model" and "Missing textures in model".^[3]
• Recipe parsing problems, such as "Failed to parse recipe" and "Error parsing recipe".^[3]
• Tag and registry chatter, such as "Couldn't load tag" and "Built tags for registry".^[3]
• Mixin messages, such as "Mixin apply failed" and "Method overwrite conflict for".^[3]
• Rules limited to one level, such as a WARN-level rule for "Texture" and an INFO-level rule for "Hiding ".^[3]

Project Infinity 0.1 0.0.51.4-hotfix-2 ships Ember's Log Filtering 1.1.2 (logfilter-forge-1.20.1-1.1.2.jar). The mod was already in the pack in 0.0.51.1 or earlier, so you have had it for a while.^[2]

1.1.2 (the version in this pack)

• Redundant leading and trailing .* are now stripped from filter patterns before they are compiled. Rules match with find(), so a wrapped pattern like .*GL_INVALID_OPERATION in glBlitFramebuffer.* defeated the literal-prefix optimization. Every non-matching log line then cost time quadratic in its length, enough to multiply modpack load times.^[4]
• A log message is only formatted when a MESSAGE_REGEX rule needs it. Disabled rules are dropped when the config loads, instead of being skipped on every log event.^[4]

1.1.1

• NeoForge LogFilter is packaged as a single bootstrap container. It initializes the filter before mod discovery and exposes its embedded normal mod to NeoForge. Rules can now filter discovery and Mixin-config messages, including missing-refmap warnings.^[5]
• Duplicate filters are no longer attached when later lifecycle fallbacks initialize LogFilter again.^[5]

Unverified Pack changelog entries for this mod are not available, so what changed for it between Project Infinity releases is unverified.