Terraria: tModLoader Logs & Debugging
Debugging a modded Terraria server can be daunting, but the **tModLoader Logs** provide a clear roadmap of exactly why a server failed to start or why a specific mod is behaving poorly. Mastering these logs is essential for maintaining a stable world with large mod-packs like Calamity or Thorium.
1. The Primary Log
Your main point of reference is server.log. It records the entire startup sequence, from the initial RAM allocation to the final "Server Started" confirmation.
2. Mod Exceptions
If a mod has a code error, it will throw an **Exception**. These are usually highlighted and will list the specific .cs file or mod name that caused the failure.
3. Handshake Errors
If players are kicked with "Connection Lost," the logs will show if it's due to a **Version Mismatch** or a missing .tmod file on the client's end.
How to Access Your Logs
- Navigate to the File Manager in the Supercraft Panel.
- Open the directory:
/executables/tModLoader-Logs/. - Locate the
server.logfile for the current session. - For past crashes, check the
Old/directory, which archives previous boot sequences.
Decoding Common Error Messages
| Error Snippet | The Meaning | The Solution |
|---|---|---|
OutOfMemoryException | The server ran out of assigned RAM. | Upgrade your plan or reduce the number of high-res texture mods. |
Mod dependency not found | Mod A requires Mod B to be installed. | Search the Steam Workshop for the missing parent mod and enable it. |
NullReferenceException | A mod tried to access a block or item that doesn't exist. | Usually caused by removing a mod from an existing world. Re-add the mod or ignore. |
System.DllNotFoundException | Missing a system runtime file. | Ensure you are running the correct tModLoader branch for your OS. |
The "Infinite Crash Loop" Fix
If your server crashes immediately upon start, it is likely trying to load a broken mod. You can fix this without deleting your world:
- Go to
/mods/in the File Manager. - Open the
enabled.jsonfile. - Delete the name of the problematic mod (e.g., "CalamityMod").
- Save the file and restart the server. This prevents the broken mod from attempting to load.
Expert Tip: When reading logs, always start from the Bottom and read upwards. The actual reason for a crash is almost always the very last "Exception" thrown before the "Server Closed" message.
Run your mod-packs with absolute confidence. Host your Terraria server with Supercraft and use our detailed logging tools to keep your community online 24/7.