# 親自解決問題(未完成的項目)

> 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?
>
> &#x20;                                                                                                                                           \--943

## Check Modlist

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.

![](https://3482869719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0cs4LD4nc6h1ZShi3DQG%2Fuploads%2FfXfijjgw0KCRJ8B3Lwat%2Fimage.png?alt=media\&token=069a46ec-d3b3-4052-9bdb-443f790c786e)

Here we note the column with LCHI or LCHE on the left, each letter carries its own meaning

| Letter                              | Meaning                                                                                           |
| ----------------------------------- | ------------------------------------------------------------------------------------------------- |
| <mark style="color:red;">'U'</mark> | Unloaded<mark style="color:red;">(Indicates that this mod was aborted while loading.)</mark>      |
| <mark style="color:red;">'E'</mark> | Errored<mark style="color:red;">(Indicates that an error occurred while loading this mod.)</mark> |
| 'D'                                 | Disabled(Indicates that this mod is a disabled mod.)                                              |
| 'L'                                 | Loaded                                                                                            |
| 'C'                                 | Constructed                                                                                       |
| 'H'                                 | Pre-initialized                                                                                   |
| 'I'                                 | Initialized                                                                                       |
| 'J'                                 | Post-initialized                                                                                  |
| 'A'                                 | Available                                                                                         |

## Deeper Analysis

![](https://3482869719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0cs4LD4nc6h1ZShi3DQG%2Fuploads%2FxXt3n9PlF7zLy294MVG9%2Fimage.png?alt=media\&token=f7f1a945-3b56-428e-840d-16feb1fd8edc)

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.

## Other issues

You can find java.lang.XXX in the next line of the Description,The following are some of the XXX representatives' questions:

### NoClassDefFoundError

#### Server side:

(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

### ClassCastException

#### both Server\&Client

Unable to perform class conversion, in layman's terms, a mod conflict

Solutions:Remove conflicting mods

### LoaderException

#### both Server\&Client

There was a problem loading the mod

Solution: Check [Check Modlist section](#check-modlist) to find Errored MODS,Replace or delete the mod/update the forge

### OutOfMemoryError

#### both Server\&Client

Solution: Increase your RAM allocation

### Exception while ticking a block

#### both Server\&Client

Solution: Find the "-- Block being ticked --" section, learn the block coordinates, and use some methods to remove the block
