安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
奖励
to my understanding, in a multiplayer environment, the unit init that the script is run through is executed by every player in the server.
because there are remoteExecuted and global commands in the script, these are run by all players and this can cause performance issues.
so if you have 12 players playing your mission, each of them would be running the script at the same time, executing commands on top of one another.
i think you should be able to make the script run server only if you add:
if (!isServer) exitWith {};
at the beginning of each unit init containing code.
that way the script should only run on the server.
correct me if i am wrong.
But i think the protest has a check if a certain variable is active on the unit. For limited use one could make a trigger, though you´d have to work the condition out, and set the variable to false to make em flee.
I'll try this out too. Thanks