Crash Reports Changes in 1.13 and above - 04Slash/Breaking-Down-Minecraft-Forge-Crash-Reports GitHub Wiki
This section is dedicated to the changes that were made within the newer versions. The 1.12 section is still important to look over as most of the information there still applies. There are some minor formatting changes and some slight changes to where to look in the newer versions of Minecraft.
Newer versions no longer follow the formatting shown in the first picture. Now, each mod’s state will be listed beside it’s version. In the second picture, this is shown as DONE. This is a crash report where all mods were loaded successfully, and the crash happened after mod loading. This is a crash report from 1.16.4. The ones shown below will be from previous versions however the information still applies, it just will be visually different. Expect the formatting to change slightly as well in the future.
In 1.14+ Forge made some more changes to the mods section of the crash report. The erroring mod will be clearly stated by having the word Errored or ERROR at the end of it (see second picture). It’s more important in these versions that you check the mods section as well as the stacktrace. In some instances, such as this crash report (or the 2 pictures above) it may list one mod in the top stacktrace xyz.vsngamer.elevatorid (or “OpenBlocks Elevator”) while showing another mod as ERROR in the mods section Apotheosis. In this situation, you should first look into the ERROR mod as that is the mod that likely is causing the issues.
It’s important to note that ERROR may not always show up. Sometimes this shows as something different. In this instance it shows as Validate. In this particular issue, the above stacktrace did not provide any useful information to fixing the issue (See here). This shows the importance of checking both the stacktrace at the top and the mods section at the bottom. The mods section seems to be more reliable and you should always look for anything that seems off down there and look into that before looking into what the stacktrace is telling you.
In the event that you download a mod but not the dependency, this will clearly be listed in the section between the top stacktrace and mods section. This should display all the information needed to download said mod dependencies. This section may also be used when multiple mods have errors when loading so it may be worth taking a look at this section as well when trying to fix crashes.
You will probably notice this datapack section. For the most part, it can be ignored. The many incompatible datapacks are nothing to worry about. It just means the mods don’t natively support datapacks at this time. Over time this may change since, at the time of writing this, we are still in the early stages of 1.13+ modded.