🚨 Fix the Jade “Please Report” Error in Minecraft Mods

If Jade shows a red “Issue found. Plz report to Jade.” warning in a tooltip, Jade has hit an error while displaying information about a block, entity, item, or another mod integration. The warning is a clue, not a diagnosis: it does not prove that Jade itself is the only mod at fault. Start by reproducing the same target, checking the active instance’s logs/latest.log, and matching Jade and related mods to the exact Minecraft version and mod loader you use.

Jade is an information HUD for Minecraft Java Edition. Its project page says it can run client-side, while some features need Jade on the server too. That distinction matters if the warning only appears in multiplayer. Check Jade’s project page and version list before changing files.

What the Jade “Please Report” error means

Jade collects information from the object you are looking at and displays it on screen. A mod can also supply Jade with extra information through an integration. If something fails while that tooltip is being prepared, Jade may show an error warning or write diagnostic output. The wording alone does not identify which component threw the exception.

Separate a tooltip warning from a full game crash. If the game keeps running, capture the warning and the object that triggers it. If opening an inventory, joining a world, or loading a server crashes the game, preserve the crash report as well as the log. Jade’s issue tracker includes a report where the tooltip warning appeared over dropped items and an inventory crash occurred in a particular server setup; that example shows why the exact trigger and environment matter, not that every player has the same cause. See the Jade issue example.

Fix the Jade error step by step

1. Record the trigger and protect your world

Write down what you were looking at when the message appeared: the block, mob, dropped item, inventory screen, or machine. Note whether it happens in single-player, multiplayer, or both. Record the Minecraft version, loader (Fabric, Forge, NeoForge, or Quilt), Jade version, and any Jade add-on or mod that provides the affected block or item.

Before removing or changing mods, back up the world and duplicate the launcher profile or modpack instance. Do not open and save a world that depends on removed mods; test changes in a disposable copy. If the error happens only on one server, compare a single-player test with that server and ask its administrator about server-side mod versions before changing your client.

2. Inspect the right log files

Reproduce the warning once, then open the active instance’s game directory and inspect logs/latest.log. A third-party launcher may use a separate game directory for each profile, so do not assume the default .minecraft folder is the one in use. Search near the time of the error for JadeErrorOutput, Exception, Caused by, and the name of the mod or integration that adds the affected content. Some reports mention a JadeErrorOutput file or folder under the logs directory; include it if your instance created one.

If Minecraft crashed, also check crash-reports for the matching report. Fabric’s crash-report guide explains how stack traces and mod lists can help narrow down a cause, while warning that a mod named in a trace is not automatically the sole culprit. Read Fabric’s crash-report guide. Keep the surrounding exception and “Caused by” lines; a lone final error line often lacks the useful context.

3. Match Jade and add-ons to your exact setup

Download Jade for the exact Minecraft release and loader used by the instance. A file for Fabric is not interchangeable with a Forge or NeoForge build, and a version for a different Minecraft release may fail even if its filename looks similar. Use the version filters on Jade’s project page, and check the release page for every add-on that participates in the tooltip.

Jade Addons are optional integrations, not a universal dependency that every installation must add. Install or update one only when you want its supported integrations and its release matches your setup. Update through the modpack’s own launcher or instructions when possible; replacing individual files in a curated pack can create a new version mismatch. Remove duplicate older JARs from the active mods folder after confirming the replacement is correct. Do not add Cloth Config, Architectury, or a Java argument just because an unrelated guide lists them—use a dependency only when the selected mod’s own release page requires it.

Review Jade’s available builds and compare the game version and loader shown for the file with the profile you actually launch.

4. Isolate the mod that supplies the failing tooltip

Use your copied instance or a disposable test world. Keep the loader, Jade, and only the dependencies listed for those files, then test whether the warning returns. If it disappears, add the remaining mods back in small batches. When the issue returns, test the last batch one mod at a time. Start with the mod that adds or changes the object that triggered the warning, plus its Jade integration if one is installed.

Change one thing per test and repeat the same action. If the message is tied to a particular block or item, removing its content mod may make that object unavailable, so use a test world and do not save over your original. When the issue occurs only on a server, compare client and server logs if available; Jade documents that some displayed features need server support, so ask the server administrator to check the relevant server-side setup rather than installing every mod on both sides blindly.

When and where to report the error

Report to Jade when the problem still reproduces with a minimal, compatible setup or the stack trace points into Jade itself. If the exception identifies another mod’s tooltip provider or integration, check that mod’s issue tracker too; the right maintainer may be the one that supplies the failing information. Jade’s own tracker asks for the latest log in bug reports. Open the Jade issue tracker.

• Include Minecraft, loader, Jade, and relevant add-on versions.
• List the exact steps and object that reproduce the warning.
• Say whether it occurs in single-player, multiplayer, or both.
• Attach latest.log, any JadeErrorOutput output, and a crash report if the game crashed.
• State whether you reproduced it with only the relevant mods.

Before posting logs publicly, review them for private server addresses, account details, or other information you do not want to share. Keep the exception context and mod list intact when removing unrelated private details.

Quick checks and prevention

Keep a backup before updating a large modpack, avoid mixing loader builds, and save the working versions when a pack is stable. Those habits make it easier to identify which update changed the behavior—and give a maintainer enough information to reproduce a Jade tooltip error in Minecraft.