Reading the log

InvocationTargetException — the real error is wrapped inside

What the log looks like

java\.lang\.reflect\.invocationtargetexception
undeclaredthrowableexception

How to fix it

  1. This exception never is the cause — it only wraps another one
  2. Read the last Caused by: block in the trace; that is the real error
SeverityBreaks something
CategoryReading the log

Check your own log

Related errors

Reading the logFabric Crash: NumberFormatException: For input string: "4 "Open `.minecraft/logs/latest.log` in a text editor and find the `[main/WARN]: Mod resolution failed` section rReading the logForge LoadingFailedException: Loading errors encounteredLook at the lines immediately inside 'Loading errors encountered: [ ... ]' to find the failing mod's name and Reading the logForge Mod Loading Crash (LoaderExceptionModCrash)Open the crash report and find the 'LoaderExceptionModCrash: Caught exception from <Mod Name>' line to see whiReading the logHarmless Server Warning: ClassNotFoundException: net/minecraft/class_5616 (registrate-fabric)Ignore [main/WARN] lines referencing net/minecraft/class_5616 (from registrate-fabric) as well as class_906 anReading the logNullPointerException: "this.cpuVendor" is null (OSHI Warning)Check that this message is marked `[main/WARN]` in your log; it does not stop Minecraft or your server from ruReading the logReportedException: Exception generating new chunkOpen your `latest.log` or crash report and scroll below `net.minecraft.ReportedException: Exception generating