When you join a tModLoader server, the game must ensure your local mods exactly match those of the host. Mod Syncing
Large modpacks require massive amounts of data exchange during the "Joining" phase. If your connection or the server's connection dips, the handshake times out silently.
If there is a discrepancy—such as a graphic setting that differs or a mod version mismatch—tModLoader forces a . The problem arises when that reload takes too long. For players with large mod packs (100+ mods) or slower hardware, reloading all mods can easily exceed 2 minutes. If the reload exceeds 120 seconds, the server times out the connection, assuming the client has disconnected. Consequently, the client finishes reloading the mods, reaches the "Reload Complete" state, but finds the server has already kicked it, resulting in the dreaded infinite loop. reload complete joining tmodloader
Shut down heavy browsers (like Chrome) and Discord hardware acceleration before joining.
You and the server have different versions of the same mod. When you join a tModLoader server, the game
Are you using any large overhaul mods like or Fargo's ? Is this a dedicated server or a Host & Play session?
: If you have manually installed a version of a mod in your local folder that differs from the server's Steam Workshop version, the sync may fail. stuck on this screen If there is a discrepancy—such as a graphic
Nothing breaks a stable mod list like an automatic update. A mod that worked yesterday may cause "reload complete joining tmodloader" to hang today because the author pushed a hotfix that conflicts with another mod.
Ensure your "Beta Participation" dropdown matches the host. If the server is on the stable release, set your dropdown to None . 5. Disable "Steam Cloud" for Mod Configs