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









We're mercenaries and love to steal things. This will also no doubt be appreciated by Antistasi players.
The fix was even easier. The createVehicleCrew command has an optional parameter for the side. Now the AI will be replaced with the side of the player connected to the UAV.
This is because when the AI is replaced, it is replaced with an original version of the AI, unaltered, based on whatever vehicle it is.
This is a problem if I have an OPFOR drone under my control while playing BLUFOR. The drone reverts to OPFOR from BLUFOR.
A solution to this would be code that does a check of the user's current side when replacing AI, and after the replacement takes place, if the side of the replaced AI is not the same, set the side of the AI to match the user.