Lognore

Lognore

Ignore spammy console logs in Minecraft 1.7.10

Prevents selected console log messages from being printed to reduce clutter. You can configure Lognore to filter messages by logger name or by message content.

Configuration

Lognore offers two filtering methods and a severity threshold control.

1. Logger Blocking

Blocks all messages from a specific Log4j logger.

How to identify a logger:
Look at the third set of square brackets at the start of a log message.

Example:
To block CraftPresence messages, extract the logger name craftpresence from this line:

[17:38:00] [CraftPresence/INFO] [craftpresence]: Configuration settings have been saved and reloaded successfully!

2. Message Blocking

Blocks any log message containing a specified substring.

Example:
Using the filter "moved too quickly" would block messages like:

• [Player123] moved too quickly!
• [Steve] moved too quickly!

3. Max Filtered Level

Sets the maximum log level to filter. Messages at or below this level will be hidden.

Available levels (highest to lowest severity):

• ERROR (most severe)
• WARN
• INFO
• DEBUG (least severe)

Default: WARN (filters WARN, INFO, and DEBUG)

Sample Configuration

# Configuration file

general {
    # Log4j loggers to filter [default: ]
    S:loggerFilters <
        craftpresence
     >

    # Max filtered log level, valid values are ERROR, WARN, INFO, DEBUG. For example, setting to WARN, would filter WARN, INFO, and DEBUG. [default: WARN]
    S:maxFilteredLevel=WARN

    # Messages to filter (substring) [default: ]
    S:messageFilters <
        moved too quickly
     >
}