More Chat History 2.0.0: Fabric 26.1–26.2 Guide

Current release check: More Chat History 2.0.0 is a client-side Fabric mod for Minecraft Java 26.1, 26.1.1, 26.1.2, and 26.2. It raises the chat-history limit from vanilla’s 100 messages to 16,384. It does not turn chat into a permanent archive or a server moderation log.

The current release file is morechathistory-2.0.0.jar. Creator metadata marks the client as required and the server as unsupported, so a player installs it in the client profile—not in a dedicated server’s mod folder.

Match the exact 2.0.0 tuple

The project’s overall loader history includes Quilt, but release 2.0.0 is labeled Fabric only. Older releases such as 1.3.1 carry Fabric and Quilt labels for older Minecraft lines. Do not use the project-level Quilt badge as proof that the current file supports a Quilt 26.2 profile.

The current creator source manifest declares Fabric Loader 0.18.4 or newer, Minecraft 26.1 or newer, and Java 25 or newer. That is a current-source boundary, not a MineBrush inspection of the published JAR. The Modrinth release record itself declares no separate dependency relations.

What the mod changes—and what it does not

More Chat History changes the maximum number of chat entries retained by Minecraft’s client chat component. The current creator source uses a fixed 16,384-entry limit in place of the vanilla 100-entry limit. This is useful during a long play session when earlier coordinates, commands, trade messages, or conversation context would otherwise fall out of the scrollback.

It does not add a search tool, export button, cloud sync, moderation database, or proof-preservation workflow. It does not reveal messages the client never received. Clearing the visible client history does not prove that a server, proxy, moderation plugin, streamer recording, screenshot, or another player deleted its own copy.

Restart persistence is not promised by the creator project description. Treat the mod as expanded client scrollback, not a substitute for notes or a properly governed server log.

Install it in a clean client profile

1. Create or duplicate a Minecraft Java profile for one of the creator-listed 26.1–26.2 builds.
2. Confirm the profile uses Fabric and a Java-25-capable runtime.
3. Check that Fabric Loader meets the current source-manifest boundary.
4. Download version ID qpDhYv1Y from the creator-controlled versions page and verify the filename before moving it.
5. Place the JAR in that client profile’s mods folder.
6. Do not install it on the dedicated server.
7. Launch with other chat-screen or chat-retention mods disabled for the first comparison.

MineBrush has not downloaded or run the 2.0.0 artifact. These steps define a reproducible player check; they are not a compatibility guarantee.

Prove the useful behavior without exposing real chat

1. Open a disposable single-player world or a private test server where generated messages are allowed.
2. Use harmless numbered test lines rather than private conversation.
3. Produce more than 100 entries, open chat, and scroll toward the first numbered line.
4. Capture only the line range and profile tuple needed to show the result.
5. Close and reopen the chat screen, then test a disconnect and a full client restart as separate events.
6. Write down which boundary retained or cleared the scrollback instead of calling the behavior “permanent.”

Do not paste private server chat, direct messages, account IDs, IP addresses, authentication tokens, private coordinates, or unredacted logs into a public report. A longer local history also means more text may remain visible during screen sharing or recording.

Troubleshoot the first failing layer

Update and rollback without losing the baseline

Keep the old profile intact. Create a second profile with the new Minecraft build, loader, Java runtime, and More Chat History file. Repeat the same numbered-message test. If the new tuple fails, return to the complete old profile rather than dropping an older JAR into a newer game.

Removing this client mod should be tested at the client-profile level. It does not authorize deleting server records, launcher data, or unrelated chat configurations. Back up any locally important notes before testing because the mod is not an export system.

No performance or privacy guarantee

Retaining more entries can change the amount of chat data available to the client, but MineBrush has no runtime measurement for memory, frame time, chat-screen responsiveness, startup, or long-session behavior. Hardware, message length, formatting, chat UI mods, and recording overlays can change the result.

CC0-1.0 is the project’s software license label. It does not turn player chat into public-domain content or grant permission to publish private conversations.

Creator-controlled sources

• More Chat History project
• Official More Chat History versions
• More Chat History 2.0.0 release
• Creator source repository
• Creator issue tracker

Download boundary: MineBrush does not mirror the JAR. Use the creator versions page, match the complete tuple, and keep private chat or logs out of DLE file history.