No Chatter

Designed with simplicity and modpack immersion in mind, NoChatter provides configurable control over unwanted chat and system messages without replacing the chat screen or altering server behaviour.

NoChatter is intended for modpack creators and players who want to hide specific repeated messages from other mods, such as setup prompts, compatibility warnings, or immersion-breaking notifications.

Rules are defined in a small JSON config file and matched against the text that would normally be shown in chat.

When unwanted chatter appears, the answer is simple: not today.

Latest Update – Version 1.0.2

NoChatter 1.0.2 adds quality of life, stability, and gameplay improvements.

Highlights

• Added a configurable option to hide chat while sleeping
• Additional stability and gameplay improvements

Features

• Hide selected chat/system messages
• Block incoming player chat globally
• Proximity filtering for player chat with a configurable range
• Hide chat while sleeping
• JSON-based configuration
• Supports simple contains and startsWith matching
• Supports rough phrase matching using containsAll
• Supports case-sensitive matching per rule
• Received-message logging for finding exact phrases
• Suppressed-message logging for testing rules
• Handles messages added directly to the client chat component
• Lightweight and safe for modpacks
• Client-side only

Typical Use Cases

• Hide repeated setup prompts from client-side utility mods
• Suppress immersion-breaking compatibility warnings
• Remove noisy modpack startup messages from chat
• Optionally hide incoming player chat while keeping system and mod messages available
• Help modpack creators polish the player experience

Configuration Guide

NoChatter is configured using:

config/nochatter.json

The file is created automatically on first launch.

Changes can be made while the game is running. NoChatter checks the config again when messages are received, so restarting is usually not required when testing new rules.

Core Behaviour

enabled

Controls whether NoChatter suppresses messages.

Default: true

If disabled, all suppression rules are ignored.

logReceivedMessages

Controls whether every received chat/system message is written to the log.

Default: false

Enable this temporarily when you need to find the exact text of a message to suppress.

logSuppressedMessages

Controls whether suppressed messages are written to the log.

Default: true

Useful while testing rules. Once your config is working, this can be disabled to keep logs quiet.

Message Rules

Rules are listed under rules.

Each rule can use one or more matching options.

label

A friendly name for the rule.

This is used in logs only.

enabled

Controls whether this individual rule is active.

Default example rules are disabled.

caseSensitive

Controls whether matching should respect upper/lower case.

Default: false

contains

Suppresses messages containing this text.

startsWith

Suppresses messages starting with this text.

containsAll

Suppresses messages containing all listed text fragments.

This is useful for rough matching when the full message may vary slightly.

blockAllPlayerChat

Suppresses all messages received through Minecraft’s player-chat channel.

Default: false

proximityPlayerChat

Limits received player-chat messages to players within the configured proximity range.

Default: false

proximityChatDistance

Sets the maximum distance, in blocks, at which player-chat messages are shown when proximity chat is enabled.

Default: 50.0

hideChatWhileSleeping

Hides the chat window and input field while sleeping without discarding received messages.

Default: false

Note – System, server and mod messages remain visible unless matched by a configured rule.

Example Config

{
  "enabled": true,
  "blockAllPlayerChat": false,
  "proximityPlayerChat": false,
  "proximityChatDistance": 50.0,
  "hideChatWhileSleeping": false,
  "logReceivedMessages": false,
  "logSuppressedMessages": true,
  "rules": [
    {
      "label": "simple_voice_chat_setup_hint",
      "enabled": true,
      "caseSensitive": false,
      "contains": "Press V to set up",
      "startsWith": "",
      "containsAll": []
    },
    {
      "label": "iv_entity_culling_warning",
      "enabled": true,
      "caseSensitive": false,
      "contains": "IV HAS DETECTED THAT ENTITY CULLING MOD IS PRESENT",
      "startsWith": "",
      "containsAll": []
    }
  ]
}

Matching Examples

Hide a message containing specific text

{
  "label": "guide_hint",
  "enabled": true,
  "caseSensitive": false,
  "contains": "Press H to open the guide",
  "startsWith": "",
  "containsAll": []
}

Hide messages from a visible mod prefix

{
  "label": "example_mod_prefix",
  "enabled": true,
  "caseSensitive": false,
  "contains": "",
  "startsWith": "[ExampleMod]",
  "containsAll": []
}

Hide a rough phrase

{
  "label": "chapter_unlock_hint",
  "enabled": true,
  "caseSensitive": false,
  "contains": "",
  "startsWith": "",
  "containsAll": [
    "You have unlocked",
    "chapter"
  ]
}

Finding Messages to Suppress

If you are unsure what text to match, temporarily enable:

{
  "logReceivedMessages": true
}

Then trigger the message in-game and check the log for entries like:

received chat source=chat_component text="[Simple Voice Chat] Press V to set up"

Copy a stable part of the text into a rule, then disable received-message logging again.

Compatibility

NoChatter is client-side only and does not require server installation.

It is designed to work with messages added through Minecraft’s client chat component, including messages that may not pass through normal chat events.

NoChatter does not replace the chat screen, block player chat globally, or modify server-side message behaviour.

Player chat can optionally be suppressed using blockAllPlayerChat. This only applies to messages received through Minecraft’s player-chat channel; system, server and mod messages remain subject to the configured rules.

Reporting Issues

If you encounter a compatibility issue with another mod, or find a machine setup that behaves incorrectly, please report it via the project issue tracker so it can be investigated.

If a message is not being suppressed, enable logReceivedMessages, reproduce the message, and include the relevant NoChatter log lines when reporting the issue.