安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
I also removed the mod dependency in About because now Legacy users were kicking up. you should be able to figure out that either one needs to be enabled without me :)
If you're still using Legacy deal with it (or change the dependency in your local copy).
if anyone is still using Legacy I'm sure they're aware of dependency issues when using forks. honestly this could have been avoided if they didn't change the packageId when moving out of Legacy, a lot of forks keep the old one for this reason 🤷🏼♀️
I don t know how exactly it s done, but it s something about the RIMPY database.
Thanks...
It s not like it s not working, just that it s very annoying to get a warning every time I sort.
I removed the mod dependancy section from the about.xml for this mod and it no longer flags the error in RimPy.