安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题








- https://psteamcommunity.yuanyoumao.com/workshop/filedetails/discussion/3161388997/600775554275296585/
- https://psteamcommunity.yuanyoumao.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.