Repository navigation
Troubleshooting
Companion 1.4.2 loads the enabled menu layers before world detection. In earlier 1.4.0 builds, waiting for a world profile could leave the first menu Vanilla.
Check that All Matcha Visuals is selected, or that Buttons, Sliders & Scrollbars is enabled, and press the root Save Changes button. Higher-priority resource packs or interface mods may override these assets. Selecting the Vanilla preset intentionally leaves optional menus Vanilla.
Those strings are translation keys sent by Matcha's gameplay data. The client needs the corresponding resource translations and sometimes custom font glyphs. From 1.4.2, the Companion keeps these available before the first world/server message and independently of optional terminology and GUI choices.
Use a supported Matcha version, confirm the Companion version, and check for conflicting full Matcha packs or language packs. Record the exact untranslated key and Matcha release when reporting a remaining issue. A similar-sounding key may be spelled differently, so copying the text is helpful.
Open settings in the affected world and read the compatibility label. Verify the Matcha version is one of the four supported releases, the gameplay data is enabled, and the relevant Creative/JEI setting is on. A title-screen theme alone does not prove the world was detected. Remote unknown signatures deliberately leave the catalogue inactive.
Check enabled world datapacks first: they take priority over an installed mod. Disable conflicting gameplay copies using Minecraft/server controls. Renaming an archive does not change its metadata or turn one Matcha release into another. Include the detected version and source in a report.
Use Save Choices in the browser, then Save Changes in the root settings. Check resource-pack priority and other texture/interface mods. Confirm that the entry is selectable rather than a locked Matcha-exclusive or Vanilla-exclusive reference. Required custom-content assets intentionally remain available.
Check Hide Plain Vanilla Duplicates under Catalogue. Plain vanilla bases and component-bearing Matcha stacks can look alike but are different stacks. Enable the setting for cleaner listings, or disable it to access both deliberately. Items already in your inventory are unaffected either way.
Install the MezzConfig GUI version for your Minecraft release. JEI includes MezzConfig, but that library alone does not provide the GUI. If Fabric refuses to launch because of an old standalone JEI or MezzConfig, update/remove the incompatible standalone copy.
Check Show Recipe Browser separately from Matcha Items in JEI. The former controls the overlay; the latter controls Matcha listings. Also check secret/unfinished-item settings. Multiplayer recipe visibility depends on server-supplied information.
Check Minecraft's Advancements keybind; the default is L. Resolve conflicts in Controls → Key Binds. A mod that replaces the entire advancement screen can bypass the vanilla layout enlarged by the Companion. The artwork toggle changes styling, not the expansion behaviour.
Companion 1.4.2 selects its configured packs before the first load and gives Windows resource-preparation workers dedicated 4 MiB stacks. This addresses the reproduced native reload failure without adding launcher arguments. Update older Companion installations to the current release. If a crash remains, include the exact Companion/Java versions and the relevant crash report or native error code with your report.
Include Companion version, Minecraft version, Matcha version, installation type (world datapack/official mod/server), the detected compatibility label, and relevant resource/interface mods. Describe what you expected and what occurred. Share only the relevant log excerpt, removing private server addresses or other personal details first.
Guide for Companion 1.4.2 · Downloads · Report a Companion issue