It sounds bizarre, but a well-documented bug in certain versions of tModLoader causes network handshakes to crash if the client and server language settings do not perfectly align, or if specific mods fail to translate local files during the "Joining" phase. On the tModLoader main menu, go to .
If you are running a local server alongside your client, ensure your system has enough free RAM to support both processes.
Steam's networking layer adds an extra wrapper to the connection. If joining via Steam Friends causes the loop, try connecting directly using the server’s IPv4 address and port (default is 7777). 5. Allocate More RAM / Switch to Stable Builds reload complete joining tmodloader
Some mods use configuration files that are not automatically synced by the server.
Sometimes the game window loses focus during the reload process, causing the engine to throttle performance. Press to switch to another window. Wait 5 seconds. Switch back to tModLoader. This often triggers the final "Join" sequence. 2. Manual Mod Synchronization It sounds bizarre, but a well-documented bug in
Are you getting an , or does the game just freeze/crash to the menu?
: "Reload Complete" is the final state before the game hands over control to the "Requesting World Data" or "Receiving Tile Data" phases. Common Issues at This Stage Steam's networking layer adds an extra wrapper to
tModLoader, especially with large mod packs (20+ mods), consumes significant RAM. If your system runs out of memory during the “reload complete” phase, the operation will stall. This is particularly common on 32-bit systems or older machines.
When you see on your screen, it signifies a major milestone in the connection handshake. Here is the breakdown of the process: