安装 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(越南语)
Українська(乌克兰语)
报告翻译问题








Working out the set up, I got interested in why there is a separate locale folder. When I unpacked the Complex12.big file, it also had a locale folder. Comparing the locale folder from the big file and the zip file using WinMerge, I did not see any difference.
This implies that instruction B.4 above can be skipped - the locale folder in the big file will work. I'm testing that now. I've deleted the locale folder in "C:\Program Files (x86)\Steam\steamapps\common\Homeworld\HomeworldRM\Data" which came from Complex12.zip. So far, I'm not getting any issues.
So at least for Complex12, as long as you provide us Steam users with a download URL, we'll be able to set up and play.
What I don't understand is the reason you want launch the game by the Launcher.
I like the Launcher. It keeps the mods I subscribe to compartmentalised.
For example, I didn't like having a stray copy of the locale folder because it is not part of the stock install. That's why I tried to find out if the big file had a locale folder. So now that I've confirmed that the locale folder in the big file works ok, I'm happy to delete the extra locale folder in the data folder. Now, my HW:RM install is back to being a stock install.
Also, it's easier to troubleshoot if the mods are compartmentalised in the big file. That's why I don't install mods that require me to add or change the stock files and folders.
I have 76561198115465316