How to Protect a Dedicated Multiplayer Server from Damage Crashes

On a modded multiplayer server, a single broken damage event from a third-party creature or custom damage source can shut down the entire server for everyone online. Damagesource is Not Null Mod is safe to use on dedicated multiplayer servers to keep gameplay stable without interrupting players.

Setting Up Server Protection

1. Stop your dedicated server cleanly before making changes to its files.

2. Confirm both DSNNULL Basic and Damagesource is Not Null Mod are inside the server's mods directory so the addon has its required base mod.

3. Start the server and watch the server console during startup to ensure everything loads without missing dependency errors.

Auditing Mobs and Server Logs

1. Once the server finishes starting, join with an operator account and run /dsnnull debug testall (or enter the command through the server console) to scan all registered living mobs for remaining null DamageSource vulnerabilities.

2. Leave the server running normally; whenever a broken damage event occurs during combat, the addon catches the null DamageSource error and replaces it with a safe damage source.

3. Periodically open the server's logs/latest.log file to review the diagnostic information logged by the addon, helping you identify which third-party mod is causing damage errors.