安裝 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(越南文)
Українська(烏克蘭文)
回報翻譯問題
1. Completely incorrect syntax for disabling AI. Arma is case-sensitive with almost everything, so I recommend you get into the habit of correctly capitalizing everything. The standard practice is using camel case. So the first word in a function or variable is lowercase, and following are capitalized for easier readability. So instead of "myexamplefunction", the right way would be "myExampleFunction". If you compared "myexamplefunction" to "myExampleFunction" inside the game, it would NOT be a match. Also, you do not need to call any scripting functions. Example below:
You were using this in all the Unit's init box:
call{this disableai "path"}
The correct way would be just:
this disableAI "PATH";
Bro enableAI "PATH";
Sis enableAI "PATH";
3. You were trying to run "disableAI" on a Group, it ONLY works on Units (soldiers, civs, don't matter, just has to be unit). If you want to disableAI on a group, you would have to do it through a forEach loop that iterates through the members of a group and assigns it to each member.
4. You were trying to call "disableAI" on a vehicle, same as above, this is a problem. If you need to disable a vehicle from going anywhere, call "disableAI" on the driver.
Sorry for the lecture, I don't like to see someone waste their time creating a decent mission just to be brought down by a few stupid lines of script.
Also, if you'd like, add me on Steam and I can send you the fixed mission file.
**SPOILER**
putting a map in one of the rooms of the Ghost Hotel and on the first floor of the building your siblings are in.
**END SPOILER**
I know the glitch you're talking about. It was one of the biggest headaches I had in making this scenario. I've tested and successfully started the scenario several times myself, but if you continue having problems running it, I'll try to upload a modified version of the scenario that completely removes the entities causing the glitch.