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






:)
This would mean the 'average Joe' could download a mission that was constructed with your mod and this player would NOT need to install another mod.
I know MYSELF, if I have download mod after mod to play a mission, I skip it and move on to another.
This would mean one less mod for players to have to download to play a mission. Let the creators get it... ;)
:)
This way, people could set up units, export the script and then in ANY map they build, they use the init field to 'activate' the pylons.
Example: [Unit_Name} ExecVM Pylon_001.SQF;
Just a thought!
:)