親自解決問題(未完成的項目)
最后更新于
这有帮助吗？
If you can't find a crash report when a crash occurs, it's better to say "I've crashed and what to do" than to go to the street and find a fortune teller to figure out why it crashed, so where to find them?
--943
For beginners, the first thing you can do is to start by looking at the bottom of the entire crash log, where there is a self-shaped table with all the modules that have been identified.
Here we note the column with LCHI or LCHE on the left, each letter carries its own meaning
'U'
Unloaded(Indicates that this mod was aborted while loading.)
'E'
Errored(Indicates that an error occurred while loading this mod.)
'D'
Disabled(Indicates that this mod is a disabled mod.)
'L'
Loaded
'C'
Constructed
'H'
Pre-initialized
'I'
Initialized
'J'
Post-initialized
'A'
Available
Why is there also a place at the top that shows the mod where the error occurred, so if I look at it from the top will I get a more detailed answer?
Yes, if we look at the sentences following Description and Caused by above, we can roughly determine who(WHAT MOD) is behind it.
You can find java.lang.XXX in the next line of the Description,The following are some of the XXX representatives' questions:
(1)The server side lacks classes and methods related to the GUI like the client side, and the client mod will show that the classes are not found when calling these methods
Solutions:Remove mods that only work on the client side
Unable to perform class conversion, in layman's terms, a mod conflict
Solutions:Remove conflicting mods
There was a problem loading the mod
Solution: Increase your RAM allocation
Solution: Find the "-- Block being ticked --" section, learn the block coordinates, and use some methods to remove the block
Solution: Check to find Errored MODS,Replace or delete the mod/update the forge
