Reading the logjava.lang.NullPointerException: Initializing game
What the log looks like
java\.lang\.NullPointerException: Initializing game
Description: Initializing game\s+java\.lang\.NullPointerException: Initializing game
How to fix it
- Read the very first 'at ...' line directly underneath 'java.lang.NullPointerException: Initializing game' (skipping any 'Not Enough Crashes' line); if it contains a mod author or mod name (such as 'dmillerw.remoteio...'), update or remove that mod.
- If you recently changed a mod configuration file—such as disabling AE2 channels or turning off items—revert that setting or remove addon mods that depend on those disabled features.
- If the top 'at' line starts with 'net.minecraft.' and includes 'handler$' (for example 'handler$zjo000$onOpenScreen'), scroll down to the 'Mixins in Stacktrace' section of the crash report and update or test removing the mods listed under that class.
- If the stacktrace only shows obfuscated 'net.minecraft.class_...' lines with no mod names, split your mods folder in half and test launching repeatedly (binary search) until you isolate the exact mod triggering the startup crash.
| Loaders | Forge, Neoforge, Fabric, Quilt, Vanilla |
|---|
| Severity | Stops the game |
|---|
| Category | Reading the log |
|---|
Check your own log