Roastd / Minecraft

critical

A Fabric mod is failing inside Connector

Applies to Forge, NeoForge.

What it looks like in your log

Fabric Mod Discovery Failed!

Paste the log or an mclo.gs link. Roastd checks it for this error and everything else it knows. IP addresses, passwords and tokens are stripped before anything is stored.

What causes it

A Fabric mod running on Forge or NeoForge through Sinytra Connector is not compatible with the translation layer.

How to fix it

Check the Connector compatibility list for the mod in the trace. Replace it with a native Forge or NeoForge build if one exists, otherwise remove it.

Why it happens

Sinytra Connector lets Fabric mods run on Forge or NeoForge by translating them at load time. It works for most mods and fails for some, usually mods that patch rendering, networking or the loader itself. When a translated mod fails, the whole Fabric mod discovery step fails, and the error names the mod in the trace.

Fix it step by step

  1. 1Find the mod in the traceThe stack trace under "Fabric Mod Discovery Failed" or the org.sinytra.connector exception names the Fabric mod being translated.
  2. 2Check the compatibility listConnector publishes a list of mods known to work, known to fail and known to need a specific version. Look the mod up before anything else.
  3. 3Prefer a native buildMany Fabric mods have a Forge or NeoForge port. Replace the Fabric jar with the native one and remove it from Connector's path.
  4. 4Remove it otherwiseA mod that Connector cannot translate does not load, and taking it out is the only way to get the server up.
  5. 5Keep Connector and Forgified Fabric API in stepConnector requires a matching Forgified Fabric API version. A mismatch there fails every Fabric mod at once.

Not sure this is your problem? Paste your log and Roastd will tell you which of these it actually matched, and what else it found.

Check your own log

Errors that travel with this one