Damagesource is Not Null Mod FAQ
10 questions players actually ask, answered.
Do I need to install DSNNULL Basic before using this mod?
Yes, this mod is an addon for DSNNULL Basic, so you must have the base mod installed first for this addon to work.
How do I know if a null DamageSource crash is happening?
You'll see your game close suddenly during combat or when creatures attack, often without a clear error message in the launcher log. Check your latest.log file for "null DamageSource" or "NullPointerException" related to damage events.
Where does this mod log the information about which mod is causing crashes?
Diagnostic information is written to your game's log file (latest.log in the logs folder). Look for entries mentioning the mod name or damage source details when a null DamageSource error is caught and handled.
Will this mod fix all my crashes?
This mod specifically handles null DamageSource errors, which are a common crash type. Other crashes from different causes won't be fixed by this addon.
Does this mod change how damage works in my game?
Only when catching an error—it replaces broken damage information with safe defaults to prevent crashes, but normal damage from working mods is unaffected.
Can I use this with mods that add custom creatures?
Yes, this mod provides wider support for third-party mod creatures and their custom damage types, helping prevent crashes when those mods have damage bugs.
What happens when the mod catches a null DamageSource error?
Instead of crashing, the mod replaces the bad damage source with a safe one and logs details about what happened, allowing you to continue playing.
Will this mod slow down my game?
No, this mod acts as a runtime safety layer and only activates when an error is detected, so it has minimal performance impact during normal gameplay.
Do I need to configure anything after installing this mod?
No configuration is required—the mod works automatically in the background to catch and handle null DamageSource errors.
If this mod catches an error, should I report it to the mod author?
Yes, check the logged diagnostic information to identify which mod is causing the null DamageSource error, then report the issue to that mod's author so they can fix it properly.