安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
Also for those who are interested I was having this issue with the MK153 Mod 0 SMAW from the RHS mod.
No you can't re-pack into anything that will subsequently be shared e.g. another workshop mod.
You do realise there's now at least 3 other great ways to make very organised modpacks that ensure you always have the latest version of a mod and it's easy for all your members to use?
1.) Make a Steam Collection that people subscribe to.
2.) Make and Arma 3 Launcher Preset that people can download, load into the A3 launcher and it will then allow all the correct mods to be downloaded from the workshop for them.
3.) Make a 'dummy'/empty mod for you group where you set all the required workshop items as dependencies within Steam. When your players download this mod and add it to the A3 launcher, it will ask them if they want to download and add all the required mods to the launcher as well.
Any plans on putting this on GitHub? I'd like to contribute to the project.