Bad Wither No Cookie – Minecraft Java Edition 1.12.2–1.21.10+

Minecraft's vanilla client broadcasts certain sound events to the entire game world regardless of the distance between the source and the player. The spawning or death of the Wither, the death of the Ender Dragon, and lightning strikes are accompanied by loud sound effects that every user on the server hears. This creates significant acoustic discomfort, especially on public servers and private technical sites with automatic boss farms. The Bad Wither No Cookie - Reloaded (BWNCR) modification solves this problem by localizing the global audio broadcasts or muting them entirely at the level of the client engine.

The core sound-suppression mechanism

The modification is integrated into the game's audio system using the Mixin toolset. Instead of trying to filter out the sounds after they have entered the shared playback queue, BWNCR intercepts the sound-effect playback packets directly before they are passed to the SoundManager. This prevents unnecessary sound resources from being loaded into the computer's memory and reduces the load on the audio subsystem.

By default, the modification localizes or completely disables the broadcast of critical global sounds. The table below lists the vanilla sound events that are subject to automatic filtering once the mod is installed:

Localization means the sound stops being global. The player will hear the Wither's explosion or a clap of thunder only when the source of the sound event is within the standard audibility radius of the vanilla sound (usually 16–32 blocks). If the event occurs at another base or several chunks away, the sound stream is blocked entirely.

The diagnostic system and the /bwncr listen command

For advanced sound management, the developer integrated the diagnostic command /bwncr listen into the modification. This command helps identify the internal names of sounds directly during gameplay, which simplifies adding third-party sound effects to the blacklist.

How the diagnostic mode works:

1.      The player enters the command /bwncr listen in the game chat.

2.      The engine activates the sound-event interceptor, which begins tracking every audio signal arriving at the client's speakers.

3.      When any sound is played near the player (for example, a mob's footsteps, a door opening, a dispenser firing, or another mod's effect), the exact identifier of the event is printed in the chat (for example, minecraft:block.wooden_door.use or minecraft:entity.zombie.step).

4.      Entering the /listen command again deactivates the diagnostic mode.

This tool is critically important for setting up large modpacks. If a third-party mod adds noisy machinery or monsters, the player can easily read off the sound's signature with /bwncr listen and add it to the configuration file.

Configuring the modification

Depending on the Minecraft version and the chosen loader, the structure of the configuration files differs. The modification supports two basic settings-file formats. (see screenshot)

Modern TOML configuration (versions 1.18.2 – 1.21.10+)

In newer game versions, the settings are stored in the file bwncr-client.toml (or bwncr-common.toml), located in the .minecraft/config/ directory. The file contains the following main parameters: (see screenshot!!!)

Legacy CFG configuration (versions 1.12.2 – 1.16.5)

For older Forge versions, the settings are written to the file badwithernocookiereloaded.cfg. The file's structure has the classic look of Forge configs:

To edit the configuration file, you must use text editors that support UTF-8 encoding (for example, Notepad++ or VS Code). The changes take effect after the game client is restarted. If the Cloth Config API is present, the settings can be changed directly from the in-game menu without editing the files manually.

Architecture and performance optimization

Starting with version 1.18.2, Bad Wither No Cookie - Reloaded is a purely client-side mod. It performs no calculations on the server and requires no synchronization on the part of the connected players.

In version v3.20.3, the developer fixed a serious sidedness compatibility issue. Previously, the sound engine's client classes could be called during initialization of the mod on a dedicated server, causing the server side of the game to suddenly terminate with a NoClassDefFoundError error. The update completely isolated the client-side Mixin classes from the server loader.

In release v3.20.4, an important optimization was implemented: the engine checks the status of a sound before modifying its volume. If the sound stream is already muted by another process or by a previous instruction from the mod, BWNCR does not perform a repeat write to the audio channel's memory. This makes it possible to avoid micro-freezes on weak processors when dozens of sound signals are suppressed at once.

Conclusion

The Bad Wither No Cookie - Reloaded modification is an effective system-level tool for players who spend a lot of time on servers with advanced automation. It eliminates the intrusive global noise, improving playing comfort without the need to interfere with the server's settings.

The mod's main limitation is the complete loss of auditory cues. The player will not learn about an attack on another player's base or about the onset of a storm (if the silenceLightning parameter is enabled), which can be critical on PvP servers or Anarchy-type servers. The closest equivalent is the vanilla volume-adjustment system in the "Friendly Creatures" and "Weather" categories, but it does not allow specific sounds to be turned off selectively (for example, muting the llama but keeping the cow) and does not support blocking third-party sounds from other mods, which makes the use of BWNCR the only option for large technological modpacks.