Skip to content

How to find out why a mod is not in the mod list

A mod is missing from the list when the loader never accepted its jar. Check four things in order. The jar must be in the mods folder of the profile you launch. The loader and the Minecraft version must match the jar. The metadata file must be valid: fabric.mod.json for Fabric, META-INF/neoforge.mods.toml for NeoForge, META-INF/mods.toml for Forge (mcmod.info on 1.12.2), with a mod id of lowercase letters, digits and underscores. And logs/latest.log gives the reason, so search it for your mod id. A log line at startup proves your code ran.

Works on Minecraft 1.20.1 to 26.3 on NeoForge; Minecraft 1.16.5 to 26.3 on Fabric; Minecraft 1.16.5 to 1.20.1 on Forge; Minecraft 1.12.2 on Forge. Each example was compiled against its loader and version before it shipped in Linen.

  1. Open logs/latest.log and search for your mod id, ‘error’ and ‘skipping’.
  2. Check the jar sits in the mods folder of the profile you launch, and that its loader and Minecraft version match the game.
  3. Check the metadata file: a lowercase mod id, a version, and the entry point or main class.
  4. Add the startup log line from this page and look for it in latest.log.
  5. If the log names a missing dependency, install it or fix the dependency list.

The example mod is examplemod in the package com.example.examplemod. Use your own mod id and package.

Fabric 1.18.2 to 1.21.1, Fabric 1.21.2 to 26.3

Section titled “Fabric 1.18.2 to 1.21.1, Fabric 1.21.2 to 26.3”

Uses:

  • LogUtils.getLogger
  • Logger.info
  • Runtime.version

src/main/java/com/example/examplemod/LoadCheckLoadCheck.java

package com.example.examplemod;
import com.mojang.logging.LogUtils;
import org.slf4j.Logger;
// Load Check: writes one line to logs/latest.log when the mod starts. If you find it there, the loader accepted your jar and ran your code.
public final class LoadCheckLoadCheck {
private static final Logger LOGGER = LogUtils.getLogger();
private LoadCheckLoadCheck() {
}
public static void log() {
LOGGER.info("Example Mod (examplemod) started on Java {}", Runtime.version());
}
}

In your main mod class, inside onInitialize:

LoadCheckLoadCheck.log();

NeoForge 1.20.1 to 1.21.1, NeoForge 1.21.2 to 26.3, Forge 1.18.2 to 1.20.1

Section titled “NeoForge 1.20.1 to 1.21.1, NeoForge 1.21.2 to 26.3, Forge 1.18.2 to 1.20.1”

Uses:

  • LogUtils.getLogger
  • Logger.info
  • Runtime.version

src/main/java/com/example/examplemod/LoadCheckLoadCheck.java

package com.example.examplemod;
import com.mojang.logging.LogUtils;
import org.slf4j.Logger;
// Load Check: writes one line to logs/latest.log when the mod starts. If you find it there, the loader accepted your jar and ran your code.
public final class LoadCheckLoadCheck {
private static final Logger LOGGER = LogUtils.getLogger();
private LoadCheckLoadCheck() {
}
public static void log() {
LOGGER.info("Example Mod (examplemod) started on Java {}", Runtime.version());
}
}

In your main mod class, inside <init>:

LoadCheckLoadCheck.log();

Uses:

  • LogUtils.getLogger
  • Logger.info
  • Runtime.version

src/main/java/com/example/examplemod/LoadCheckLoadCheck.java

package com.example.examplemod;
import org.apache.logging.log4j.LogManager;
import org.apache.logging.log4j.Logger;
// Load Check: writes one line to logs/latest.log when the mod starts. If you find it there, the loader accepted your jar and ran your code.
public final class LoadCheckLoadCheck {
private static final Logger LOGGER = LogManager.getLogger();
private LoadCheckLoadCheck() {
}
public static void log() {
LOGGER.info("Example Mod (examplemod) started on Java {}", Runtime.version());
}
}

In your main mod class, inside onInitialize:

LoadCheckLoadCheck.log();

Uses:

  • LogUtils.getLogger
  • Logger.info
  • Runtime.version

src/main/java/com/example/examplemod/LoadCheckLoadCheck.java

package com.example.examplemod;
import org.apache.logging.log4j.LogManager;
import org.apache.logging.log4j.Logger;
// Load Check: writes one line to logs/latest.log when the mod starts. If you find it there, the loader accepted your jar and ran your code.
public final class LoadCheckLoadCheck {
private static final Logger LOGGER = LogManager.getLogger();
private LoadCheckLoadCheck() {
}
public static void log() {
LOGGER.info("Example Mod (examplemod) started on Java {}", System.getProperty("java.version"));
}
}

In your main mod class, inside onInitialize:

LoadCheckLoadCheck.log();

Uses:

  • LogManager.getLogger
  • Logger.info
  • System.getProperty

src/main/java/com/example/examplemod/LoadCheckLoadCheck.java

package com.example.examplemod;
import org.apache.logging.log4j.LogManager;
import org.apache.logging.log4j.Logger;
// Load Check: writes one line to logs/latest.log when the mod starts. If you find it there, the loader accepted your jar and ran your code.
public final class LoadCheckLoadCheck {
private static final Logger LOGGER = LogManager.getLogger();
private LoadCheckLoadCheck() {
}
public static void log() {
LOGGER.info("Example Mod (examplemod) started on Java {}", System.getProperty("java.version"));
}
}

In your main mod class, inside <init>:

LoadCheckLoadCheck.log();

Uses:

  • LogManager.getLogger
  • Logger.info
  • System.getProperty

src/main/java/com/example/examplemod/LoadCheckLoadCheck.java

package com.example.examplemod;
import org.apache.logging.log4j.LogManager;
import org.apache.logging.log4j.Logger;
// Load Check: writes one line to logs/latest.log when the mod starts. If you find it there, the loader accepted your jar and ran your code.
public final class LoadCheckLoadCheck {
private static final Logger LOGGER = LogManager.getLogger();
private LoadCheckLoadCheck() {
}
public static void log() {
LOGGER.info("Example Mod (examplemod) started on Java {}", System.getProperty("java.version"));
}
}

In your main mod class, inside preInit:

LoadCheckLoadCheck.log();

Linen’s How-tos library has this page too, with the example for your own mod’s loader and Minecraft version. Hover a name in your code and Linen points to the how-tos that explain it. Both are free. Download Linen.