Troubleshooting mod development
This page is about building and running Plexus Mods. If you play with mods, see If something goes wrong in the install guide and the Player FAQ.
Mod development
| Symptom | Cause and fix |
|---|---|
Plugin dev.plexusmodloader.mod not found, or a dev.plexusmodloader:… artifact cannot be resolved | Gradle could not reach the website's Maven repository https://www.plexusmc.net/maven/, or the version in build.gradle.kts is not published there. Check your internet connection and the version. Once everything is in the Gradle cache, you can build offline with --offline. With -PplexusLocalSdk, Gradle looks in Maven Local first. See Get the mod template. |
Plexus Mod Loader launch stopped in phase … | Look up the error code in the log (PLEXUS-…) in the error code table. An entrypoint exception is PLEXUS-ENTRYPOINT-003. |
PLEXUS-CONTENT-002 | You declared content after the entrypoint finished (for example, inside an event). Move the declaration into the entrypoint. |
PLEXUS-METADATA-… | plexus.mod.json is invalid. build tells you which field. |
PLEXUS-DEPENDENCY-007 | No entry in the minecraft list of plexus.mod.json matches the game version that is running. Fix the list (Write the version) or run with a matching version. |
Minecraft … is not supported by this Plexus Mod Loader build; supported: [...] | You set plexusMinecraft (gradle.properties or -PplexusMinecraft) to a version the Plexus Mod Loader you use does not support. Pick one from the supported list in the message. |
runServer fails with The Minecraft dedicated server requires accepting the Minecraft EULA | run/server/eula.txt does not contain eula=true. Plexus Mod Loader does not accept for you. Read the EULA yourself, and if you agree, create that file yourself. |
| Texture is a purple and black checkerboard | The mod ID or folder name in the model or texture path is wrong. checkPlexusResources in build reports missing models and textures and missing namespaces, file by file (Mod Development Tools). |
PLEXUS-RESOURCE-004 to 009 (during build) | A problem with a resource file name, JSON, a reference, a translation, or a plexusResources declaration. The message tells you the path to fix. |
| Breaking a block drops nothing | data/<mod>/loot_table/blocks/<block>.json is missing. |
No data fixer registered for <mod mob> | You can ignore it. The game logs this at startup for mod entities it has no data conversion for. |
| Authentication error logs for Realms or online servers | Expected, because development runs use an offline account. |
Recover the run environment
| Symptom | Where to look | What to do |
|---|---|---|
Plexus Mod Loader launch stopped in phase … | The error code in the console and in run/<side>/logs/latest.log | Look it up in the error code table, then fix or remove the mod concerned. |
| A mod is not loaded | blockedFiles and foreignMods in run/<side>/.plexus/startup-report.json | Check the per-feature PLEXUS-COMPAT-* reason. |
A Fabric mod fails when a game class loads (PLEXUS-COMPAT-133) | The log message names the class, the mixin, and its mod | Remove that mod or try a newer version of it. |
| Something odd with transforms | .plexus/transformation-report.json, -Dplexus.transformDumpDir=<dir> | If you suspect the cache, run with -Dplexus.transformCacheDir=none and compare. Corrupted cache entries are discarded automatically. |
| Download hash mismatch | ~/.gradle/caches/plexus-minecraft | Delete the file and run again. |
| You suspect world corruption | <world>/plexus/mods.properties, the game's backups/ | Plexus Mod Loader backs up a world before loading it if mods were removed or versions changed. See Operations. Still, back up important worlds yourself before you run. |
Startup errors (PLEXUS-BOOTSTRAP)
These are errors that occur while Plexus Mod Loader prepares the launch configuration, the game jar, the version adapter, and the game layer. The list of codes is in Error codes.
| Code | Cause shown in the log | What to do |
|---|---|---|
PLEXUS-BOOTSTRAP-001 | The game jar has no version.json, or the jar cannot be read | Check that plexus.gameJar points to a Minecraft game jar. |
PLEXUS-BOOTSTRAP-002 | no version adapter for Minecraft …: no version adapter handles the game jar's version. The message lists the versions this Plexus Mod Loader supports | Run a game of a supported version. In a mod project, pick it with plexusMinecraft. |
PLEXUS-BOOTSTRAP-003 | invalid launch configuration: …: a required system property (plexus.launchTarget, plexus.gameJar) is missing, the plexus.launchTarget value is wrong, or the plexus.gameJar file does not exist. The launcher exits with code 2 | Check the launcher system properties below. The Gradle run tasks set these values automatically. |
PLEXUS-BOOTSTRAP-004 | A game layer class is outside the dev.plexusmodloader.game.layer package, is not on Plexus Mod Loader's classpath, or is not in the jar | The version adapter brings in the game layer jar as a runtime dependency. If you built the classpath yourself, check that the game layer jar for that version (plexus-game-v26_2) is present. |
PLEXUS-BOOTSTRAP-005 | An exception occurred while creating or starting the game layer | Check the cause exception that follows in the log. |
Launcher system properties
The Plexus Mod Loader launcher (dev.plexusmodloader.bootstrap.PlexusLauncherMain) takes its settings as Java system properties (-D…). The Gradle run tasks (runClient, gameTests, and so on) set the values below automatically, so you only need to care about them when you start the launcher yourself.
| Property | Meaning | Default | Value the Gradle run tasks set |
|---|---|---|---|
plexus.launchTarget | One of client, dedicated_server, game_test_server | None (required) | Differs by task |
plexus.gameJar | The Minecraft game jar | None (required) | The downloaded and verified jar |
plexus.modsDir | Mods folder | mods | <run directory>/mods |
plexus.devModJars | More mod jars to load, separated by the path separator (; on Windows, : elsewhere) | None | The mod project's jar |
plexus.reportDir | Plexus Mod Loader report directory | .plexus | Default |
plexus.transformCacheDir | Transform cache directory. none turns the cache off | <plexus.reportDir>/transform-cache | build/plexus/transform-cache |
plexus.transformCacheMaxMegabytes | Upper limit for the transform cache size (MiB). When exceeded, the least recently used entries are deleted first | 256 | Default |
plexus.transformDumpDir | Directory to write the classes before and after transformation | None (nothing written) | Not set |
Relative paths are relative to the JVM working directory. The Gradle run tasks use the run directory (run/client and so on) as the working directory. The launcher passes the remaining program arguments to Minecraft unchanged.
Diagnostic reports
On every run, Plexus Mod Loader writes reports to .plexus/ in the game directory.
| File | Contents |
|---|---|
.plexus/startup-report.json | Loaded mods, blocked files, active systems, and the transform plan |
.plexus/transformation-report.json | Classes actually transformed, hashes before and after, and whether the cache was used |
At startup, Plexus Mod Loader writes a [Plexus Mod Loader] Phase … log line for each phase. The order is BOOTSTRAP (check the game jar) → DISCOVERY (find and classify mods) → METADATA_VALIDATION → DEPENDENCY_RESOLUTION (dependency and link checks) → CONFLICT_RESOLUTION (system replacement) → TRANSFORMATION_PLANNING → SYSTEM_REGISTRATION → LIFECYCLE_INITIALIZATION (Plexus Mod entrypoints) → GAME_LAUNCH. Fabric mods follow Fabric Loader's timing instead: preLaunch runs before the game starts, and main, client and server run later, inside the game's own startup. If startup stops, the phase name in launch stopped in phase … tells you where it stopped.
Report a bug
If this page does not help, report the bug on GitHub Issues. Include the error code (PLEXUS-…) and a link to logs/latest.log or the crash report; the two reports above help too. The maintainers read every report.