Once the files are present, the game must "Reload" its internal database to register the items, NPCs, and logic of those specific mods. Common Issues After Reloading
Some mods have "Server Side" configurations. If your local config file has settings that conflict with the server’s mandatory rules, the handshake might fail immediately after the reload is finished. 3. Memory Overload (RAM)
Ensure both parties are either on "None" (Stable) or the same specific version (like "1.4.4-preview"). Increase Allocated RAM If the game crashes after reloading: reload complete joining tmodloader
Even a minor sub-version difference (e.g., v1.4.2 vs v1.4.3) can cause a connection failure. While tModLoader tries to update these automatically, "Steam Workshop" lag can sometimes prevent the newest version from being recognized. 2. Config File Discrepancies
If you are stuck after the reload, follow these steps to clear the bottleneck: Clear Your "Mods" Folder Once the files are present, the game must
Use the "Export Mod List" feature in the Mods menu to give your friends a file they can import.
Ensure you are using the of tModLoader (standard for 1.4+ versions). While tModLoader tries to update these automatically, "Steam
Try joining the server again. This forces tModLoader to download a "clean" set of mods directly from the host. Check the tModLoader Version Ensure you and the host are on the same branch. Right-click in Steam. Go to Properties > Betas .
Many players find that even after the "Reload Complete" message appears, they are kicked back to the main menu or get stuck on a "Joining..." screen. This usually happens for three reasons: 1. Mod Version Mismatch
When you join a tModLoader server, your client must match the server's environment exactly. Unlike vanilla Terraria, where the game data is static, tModLoader is dynamic.