No Chat Reports in Project Infinity 0.1

Project Infinity 0.1 0.0.51.4-hotfix-2 ships version 1.20.1-v2.2.3 · First seen in 0.0.45.4

Checked Sep 17, 2026Project Infinity 0.1 0.0.51.4-hotfix-2Sources: Project Infinity 0.1 0.0.51.4-hotfix-2 modlist.json · Modrinth

Report a mistake on this page

Also in 4 other packs →

No Chat Reports is a mod in Project Infinity 0.1 0.0.51.4-hotfix-2, where it is version 1.20.1-v2.2.3. Makes chat unreportable (where possible) (Summary from the mod's Modrinth page.)

No Chat Reports guide for Project Infinity 0.1

Written for Project Infinity 0.1 0.0.51.4-hotfix-2 · also fits 0.0.45.4 to 0.0.51.4-hotfix-1 · updated Oct 15, 2026

Last verified for Project Infinity 0.1 v0.0.51.4-hotfix-2 on Oct 16, 2026 · text last changed Oct 15, 2026

Also applies to:All the Mods 10 0.32 to 8.3All the Mods 10: To the Sky 1.0 to 2.1.0All the Mods 11 0.1.0 to 0.12.0-betaAll the Mons 0.3.0-beta to 1.3.0

Sections
5

2 sections are written for this pack; 3 are shared from another pack's guide.

Every recipe and number here was checked against Project Infinity 0.1 0.0.51.4-hotfix-2, read from the running game on Sep 19, 2026.

What is No Chat Reports?

2 parts

Same as in the All the Mods 10 8.1 guide

No Chat Reports strips the cryptographic signatures that Minecraft attaches to every chat message from 1.19 onwards. Without them, your messages can't be tracked and tied back to your Minecraft client, and by extension your Microsoft account. Since 1.19.1 the mod also disables Player Chat Reporting.[1]

The pack ships version 1.21.1-v2.9.1, the NeoForge build for Minecraft 1.21.1. It's a quality-of-life and privacy mod, not a gameplay one, so it adds no items, machines or progression steps.[2]

Who it's for

It's for you if you don't want your chat history linked to your account, whether you play singleplayer, join servers, or run your own. The mod works on the client, the server, or both, and what it does depends on where it's installed.[1]

  • Client only: your client refuses to send your account's public key and strips signatures from your messages, so there's no proof they came from your account. The server relays them unless enforce-secure-profile is true in server.properties, which is the default since 1.19.1.[1]
  • Server only: clients still attach signatures, but the server strips them before relaying messages, so chat reporting doesn't work for anyone who joins. The config can also convert player messages to system messages, so players without the mod don't see them flagged as "Not Secure".[1]
  • Both sides: signatures are stripped on the client and the server doesn't try to verify them. Chat reporting and "Only Show Secure Chat" stop working, and players are told the mod disabled them.[1]
Watch out: The mod only stays effective on the client if the server allows it. The author deliberately doesn't integrate exploits to get around servers that enforce chat signing. On 1.19.3 or higher, you can still join such a server, but you can't use chat-related commands (other commands still work).[1]

Other things to know

When installed on the client, the mod also disables Telemetry. Its settings live in a NoChatReports subfolder of the config folder, split across NCR-Client.json (client-side), NCR-Common.json (server-side), NCR-Encryption.json (chat encryption, client only) and NCR-ServerPreferences.json (per-server signing modes).[1]

Unverified The sources I have don't show any quests, an ATM Star path role, or any pack-specific config changes for this mod, so I can't say whether the pack changes the mod's defaults.

How do you get started with No Chat Reports?

2 parts

Same as in the All the Mods 10 8.1 guide

No Chat Reports is a different kind of mod from the ones you'll be crafting with. There's nothing to build first. It strips the cryptographic signatures from the chat messages you send, so they can't be tied to your Microsoft account, and it also disables Player Chat Reporting.[1][3]

Unverified No recipes or quests for this mod were found in the pack's data, so there are no crafting steps or quest milestones to follow here.

What to do first

  1. Check which side you're on. With the mod on the client only, it refuses to send your account's public key and strips signatures from your messages. On a server only, it strips signatures before relaying messages to other players. With both, the server won't try to verify signatures at all.[1]
  2. Know what happens on servers that enforce signing. The server's enforce-secure-profile option defaults to true. On 1.19.3 or higher you can still join such a server, but you can't use chat-related commands. Other commands still work.[1]
  3. If you can't join a Paper or Velocity server, look for the No Chat Reports toggle in the multiplayer menu. It disables most of the mod's client-side functionality, and the mod's own tooltip says you may need to do this on those servers because they are known to cause issues.[3]
  4. Pick a signing mode if a server asks for signatures. In prompt mode your messages aren't signed by default, but if the server demands signing you get a pop-up where you can enable it for one session. Always mode signs as soon as you join, like a vanilla client. Never mode ignores every signing request.[3]

Optional: chat encryption

The mod also has an encryption feature for your messages. Right-click the encryption button to configure it. While encryption is on, you can hold a key when sending a message to skip encryption for that one message.[3]

You can generate a random key with the dice button. For AES, the key is 128 bits of Base64-encoded binary data. If you'd rather use a passphrase, pick a strong one, because not every algorithm supports passphrases.[3]

Tip: Turning off the encryption button doesn't turn off encryption itself. Switch encryption off in its own settings if you want it gone.[3]
Watch out: The mod only stays effective on the client if the server allows it. Servers that enforce chat signing and fully support reporting will still get their way.[1]

How does No Chat Reports work?

5 parts

Same as in the All the Mods 10: To the Sky 2.0.4 guide

No Chat Reports is a chat mod, and the sources currently describe no machines, multiblocks, power, fluids or item automation for it. What they do cover is what it does to your chat messages and how your client talks to a server, so that is what this section explains.[1]

What it does to your messages

Since 1.19, every chat message carries a cryptographic signature. The mod strips those signatures, which makes it impossible to track your messages and tie them to your Minecraft client and your Microsoft account, where possible. As of 1.19.1 it also disables Player Chat Reporting.[1][4]

It can only do this where the server allows it. The author deliberately does not integrate exploits that would override a server's will, so if a server enforces chat signing, the mod stays effective on the client only if the server lets it.[1]

Client, server or both

The mod can be installed on the client, the server or both, and it behaves differently in each case.[1]

  • Only on the client: your client refuses to send your account's public key and strips signatures from what you send, so there is no proof a message came from your account. The server relays the messages unless enforce-secure-profile is true in server.properties, which has been the default since 1.19.1.[1]
  • Only on the server: clients still attach signatures, but the server strips them before relaying, so reporting does not work for any player who joins. The config can also convert player messages to system messages so players without the mod do not see them as "Not Secure".[1]
  • On both: according to the project page, signatures are stripped before sending and the server does not try to verify them. Chat reporting and "Only Show Secure Chat" will not function, and players are told the mod disabled those features when they try to use them.[1][4]

The mod can also be configured to demand that it is installed on the other side too. On servers that require signed messages, 1.19.3 or higher lets you still join but not use chat-related commands, while other commands keep working. On 1.19.1 and 1.19.2 you cannot join unless you agree to send signed messages. If the mod is on the client, it also disables Telemetry.[1]

Signing modes

In the chat screen, the safety status button lets you left-click to cycle between signing modes for the server you are on. The mod's own text describes these modes:[4]

  • Always: as the mod describes it, signing is enabled as soon as you enter the server, the same way a vanilla client behaves.[4]
  • Prompt: messages are not signed by default, but if the server demands signing you can get a pop-up where you may enable it for one session only.[4]
  • On Demand: like Prompt, but signing is switched on automatically once the server demands it, with no pop-up.[4]
  • Never: messages are never signed and server requests to sign are ignored.[4]
  • Cannot Enable: your messages cannot be signed at all, either because you use an offline account or because the client failed to fetch your signing keys from Mojang's service.[4]
  • Default: shows the default mode in brackets.[4]

Reading the safety status

The same button gives the mod's assessment of how safe chatting is on the server you are on. Secure means the server has the mod or otherwise prevents reportable messages. Singleplayer and self-hosted LAN worlds are always safe. An insecure status means the server demands signed messages, which can be used against you in a report. If the server allows unsigned messages but has no protection, vanilla clients still send signed messages and show unsigned ones as "Unverified". Until the mod has evaluated a server, the status is unknown until you send a message.[4]

A "Safe Server" icon shows when the mod could verify that a server has it installed or prevents chat reports in some other known way. The server can send extra data during pings to make that work.[4]

Watch out: Realms is different. The mod's text says chat signing is always enabled there and that there is no way to prevent chat reports on Realms. The only protection it suggests is chat encryption.[4]

Chat encryption

The mod can encrypt your messages with a secret key. Only people who know the key can decrypt them, and the mod automatically decrypts encrypted messages when a suitable key is provided and the feature is enabled. You set the algorithm and key in the Encryption Settings screen. A dice button generates a new random key for the selected algorithm, and the screen reports whether key validation passed or failed.[4]

For AES, the key is 128 bits of Base64-encoded binary data. Instead of a random key you can derive one from a passphrase, but not every algorithm supports passphrases, so choose a strong one if you use it. The encryption tooltip shows whether encryption is on, and you can hold a key while sending to skip encryption for that one message.[4]

Watch out: Encryption is not a magic wand. Moderators on third-party servers can mute or ban you for what looks to them like a garbled mess in chat. The mod recommends a custom key shared only through secure channels.[4]

Unverified The mod keeps its settings in config files (client, common/server, encryption and per-server signing modes), but the sources here do not show any config files or values for this pack. Check the mod's config folder in your install to see what is actually set.

Which No Chat Reports config options matter?

3 parts

No Chat Reports keeps its settings in three files, one each for the client, for both sides (common), and for chat encryption. Here is how this pack sets the options you are most likely to look at.[5][6][7]

Client options

These live in the client file. The mod is switched on with enableMod set to true, and defaultSigningMode is set to "PROMPT".[7]

Common options

Encryption options

Chat encryption is off in this pack: enableEncryption is false. The rest is already prepared, though. algorithmName is "AES/CFB8+Base64", encryptPublic is true, and encryptionPassphrase is empty, while encryptionKey already holds a value.[6]

The interface options showEncryptionButton and showEncryptionIndicators are true, and skipWarning is false. The encryptableCommands list covers commands such as msg, w, whisper, tell and me.[6]

Unverified The sources do not say which of these values differ from the mod's own defaults, so none of them can be called a pack change.

What changed in No Chat Reports between versions?

2 parts

Project Infinity 0.1 0.0.51.4-hotfix-2 ships No Chat Reports build 1.20.1-v2.2.3, the newest build in the mod's changelog. It was first included in the pack in 0.0.45.4 or earlier, so you have had it for a while.[8][9]

Recent builds

  • 1.20.1-v2.2.3 (the build in this pack): fixed a server ping crash.[8][9]
  • 1.20.1-v2.2.2: improved config I/O error handling and logging. The changelog format also moved to Markdown.[8][10]
  • 1.20.1-v2.2.1: the initial 1.20.1 port, plus an updated Traditional Chinese translation.[8][10]
  • 1.20-v2.2.0: the initial 1.20 port.[8][10]

Earlier 1.19.4 builds

These came before the mod moved to 1.20, so they are history rather than what you run in the pack. The notable fixes are listed here.[8][10]

  • 1.19.4-v2.1.6: removed an unnecessary debug log that was accidentally left in the previous update.[8][10]
  • 1.19.4-v2.1.5: fixed a decryption issue with custom chat formats that use a full-width colon. English, Vietnamese and German translations were also updated.[8][10]
  • 1.19.4-v2.1.2: the logger name changed to "NoChatReports" (it used to show as "NCRCore"). This build also fixed errors when Mod Menu is installed without Cloth Config API, and fixed the wrong key shown for the encryption bypass shortcut on MacOS.[8][10]
  • 1.19.4-v2.1.2 also fixed misaligned custom buttons in the multiplayer menu and reworded the singleplayer safety status to reflect that self-hosted LAN servers are also safe. It added /message and /reply to the default list of encryptable commands too.[8][10]
  • 1.19.4-v2.1.2 stopped shipping Fabric's annotation classes, which should fix related mod conflicts on Forge.[8][10]
  • 1.19.4-v2.1.3 and v2.1.4 only updated translations (Thai, Polish and Korean).[8][10]

Unverified No pack changelog entries for this mod were available, so it is unverified whether the pack changed any of its behavior or settings. The mod changelog text available here is also cut off after build 1.19.4-v2.1.2, so older builds are not covered.

Sources

  1. No Chat Reports project page (modrinth) · official mod data
  2. All the Mods 10 8.1 mod list · pack file
  3. nochatreports tooltips and descriptions (English lang file) · official mod data
  4. nochatreports names, screen text and descriptions (English lang file) · official mod data
  5. Project Infinity 0.1 0.0.51.4-hotfix-2 config: config/NoChatReports/NCR-Common.json · pack file
  6. Project Infinity 0.1 0.0.51.4-hotfix-2 config: config/NoChatReports/NCR-Encryption.json · pack file
  7. Project Infinity 0.1 0.0.51.4-hotfix-2 config: config/NoChatReports/NCR-Client.json · pack file
  8. No Chat Reports 1.20.1-v2.2.3 changelog · changelog
  9. Project Infinity 0.1 0.0.51.4-hotfix-2 mod list · pack file
  10. No Chat Reports 1.20.1-v2.2.2 changelog · changelog
Where this guide comes from

Written from what Project Infinity 0.1 itself ships: its files and recipes, the in-game guidebooks and the mods' own pages. Every statement links to the source it came from, and the numbers are checked against the pack before publishing.

Guide last verified Oct 16, 2026.

Was this helpful?

Report wrong info

A few words are enough, up to 500 characters. Please do not include personal details.

Version in each release

23 releases, first in 0.0.45.4
Project Infinity 0.1VersionJarWhere it came from
0.0.51.4-hotfix-2
Sep 16, 2026
1.20.1-v2.2.3NoChatReports-FORGE-1.20.1-v2.2.3.jarFrom the published release
0.0.51.4-hotfix-1
Sep 15, 2026
1.20.1-v2.2.3NoChatReports-FORGE-1.20.1-v2.2.3.jarFrom the published release
0.0.51.4
Sep 14, 2026
1.20.1-v2.2.3NoChatReports-FORGE-1.20.1-v2.2.3.jarFrom the published release
0.0.51.3-HOTFIX
Aug 16, 2026
1.20.1-v2.2.2NoChatReports-FORGE-1.20.1-v2.2.2.jarFrom the published release
0.0.51.3
Aug 15, 2026
1.20.1-v2.2.2NoChatReports-FORGE-1.20.1-v2.2.2.jarFrom the published release
0.0.51.2
Aug 11, 2026
1.20.1-v2.2.2NoChatReports-FORGE-1.20.1-v2.2.2.jarFrom the published release
0.0.51.1
Jul 31, 2026
1.20.1-v2.2.2NoChatReports-FORGE-1.20.1-v2.2.2.jarFrom the published release
0.0.50.2-hotfix
Jun 22, 2026
1.20.1-v2.2.2NoChatReports-FORGE-1.20.1-v2.2.2.jarFrom the published release
0.0.50.1
Jun 18, 2026
1.20.1-v2.2.2NoChatReports-FORGE-1.20.1-v2.2.2.jarFrom the published release
0.0.50.0
Jun 16, 2026
1.20.1-v2.2.2NoChatReports-FORGE-1.20.1-v2.2.2.jarFrom the published release
0.0.49.3
May 17, 2026
1.20.1-v2.2.2NoChatReports-FORGE-1.20.1-v2.2.2.jarFrom the published release
0.0.49.2
May 13, 2026
1.20.1-v2.2.2NoChatReports-FORGE-1.20.1-v2.2.2.jarFrom the published release
0.0.49.1
May 11, 2026
1.20.1-v2.2.2NoChatReports-FORGE-1.20.1-v2.2.2.jarFrom the published release
0.0.49.0
May 10, 2026
1.20.1-v2.2.2NoChatReports-FORGE-1.20.1-v2.2.2.jarFrom the published release
0.0.48.2
Apr 23, 2026
1.20.1-v2.2.2NoChatReports-FORGE-1.20.1-v2.2.2.jarFrom the published release
0.0.48.1
Apr 12, 2026
1.20.1-v2.2.2NoChatReports-FORGE-1.20.1-v2.2.2.jarFrom the published release
0.0.48.0
Apr 11, 2026
1.20.1-v2.2.2NoChatReports-FORGE-1.20.1-v2.2.2.jarFrom the published release
0.0.47.3
Mar 6, 2026
1.20.1-v2.2.2NoChatReports-FORGE-1.20.1-v2.2.2.jarFrom the published release
0.0.47.1
Feb 2, 2026
1.20.1-v2.2.2NoChatReports-FORGE-1.20.1-v2.2.2.jarFrom the published release
0.0.47.0
Feb 1, 2026
1.20.1-v2.2.2NoChatReports-FORGE-1.20.1-v2.2.2.jarFrom the published release
0.0.46.1
Jan 6, 2026
1.20.1-v2.2.2NoChatReports-FORGE-1.20.1-v2.2.2.jarFrom the published release
0.0.46.0
Jan 4, 2026
1.20.1-v2.2.2NoChatReports-FORGE-1.20.1-v2.2.2.jarFrom the published release
0.0.45.4
Dec 23, 2025
1.20.1-v2.2.2NoChatReports-FORGE-1.20.1-v2.2.2.jarFrom the published release

"From pack files" means the list came from the pack's own files; "from the published release" means ForgeBase read the jars of the release itself.

Items and blocks

We can't match this mod to the pack's item list: it registers as nochatreports, and the pack's recipe dump has nothing under that name. That means we found nothing, not that the mod adds nothing. Search the item browser

Config options (how Project Infinity 0.1 sets them)

32 settings this pack ships for the mod. We don't have the mod's own defaults to compare them against yet.

See all 32 settings →

Show settings
SettingProject Infinity 0.1 value
alwaysHideReportButton
config/NoChatReports/NCR-Client.json
false
defaultSigningMode
config/NoChatReports/NCR-Client.json
PROMPT
demandOnServer
config/NoChatReports/NCR-Client.json
false
disableTelemetry
config/NoChatReports/NCR-Client.json
true
enableMod
config/NoChatReports/NCR-Client.json
true
hideInsecureMessageIndicators
config/NoChatReports/NCR-Client.json
true

Comments and tips

Loading comments...