Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
- https://steamhost.cn/steamcommunity_com/workshop/filedetails/discussion/3161388997/600775554275296585/
- https://steamhost.cn/steamcommunity_com/workshop/filedetails/discussion/3161388997/600775554275285526/
It might be due to a bad network connection, or possibly caused by another mod interfering with network behavior.
If you suspect it's caused by the COmod, you can find its log file at the following path:
`steamapps\common\tModLoader\tModLoader-Logs`
You can share the log file with me via a cloud platform like Google Drive. I’ll analyze it when I have time and perform any necessary maintenance or updates.
But honestly, I think it's more likely to be caused by something else, such as a poor network connection.