How to Find Which Mod Causes Null DamageSource Errors

When another mod triggers a broken damage event, Damagesource is Not Null Mod stops your game from closing by swapping the bad damage source with a safe replacement. Behind the scenes, it also records diagnostic details so you can track down the offending mod.

Locating Your Game Log

1. Keep playing normally until you fight modded creatures or trigger custom damage effects where you suspect broken damage events occur.

2. To reach your game folder quickly from inside Minecraft, press Esc, go to Options, select Resource Packs, and click Open Pack Folder.

3. Navigate up one folder level to your main Minecraft directory, then open the logs folder.

4. Open latest.log using any plain text editor. If you already closed and restarted the game, check the archived log file from that session instead.

Identifying the Problem Mod

1. Use your text editor's search shortcut (Ctrl+F or Cmd+F) to look for diagnostic entries related to null damage sources.

2. Read the details logged at the moment the addon caught the error and substituted a safe damage source.

3. Note the creature or custom damage details in those lines to see which third-party mod caused the issue.

Once you know which mod is responsible, you can decide whether to adjust its settings or remove it from your modpack.