Skip to content

Documentation

Errors explained

Every error message says what to try next. When the game closes with an error, the launcher reads the log and the crash report, recognizes the cause and offers the fix in one button.

Crash diagnosis

The launcher recognizes what the loaders and the JVM say:

  • A dependency missing or in the wrong version.
  • A mod made for another Minecraft or loader; a duplicated mod id; a failed mixin.
  • Exhausted memory; a newer Java required; a driver that refused the window.
  • The mods the crash report itself suspects.

The fix in one button

  • Install the dependency, update the mod or disable it.
  • Adjust the memory, download the Java, reinstall the version.
  • Go back to the last snapshot. What is not recognized still shows up, with the rollback.
  • A closing with an error warns with a link to the diagnosis; the sessions card offers the same for any stored log.

If the launcher does not even open

  • The error screen says why, and the same text is in nao-iniciou.txt in the data folder (%APPDATA%\DromorCraft on Windows, ~/.local/share/dromorcraft on Linux).
  • Every run leaves a file in logs/. Bring that file to Discord or open an issue; the answer comes faster.
  • A task that fails warns you wherever you are.