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









if not thats alright thanks for your time.
Sorry, I honestly don't know mate, I would assume that if the modules are placed into the mission file then it would cause a dependency, but I'm not sure if simply having the mod active while creating a mission would cause a dependency for that mission file.
If you want to use it via Zeus, then both client and server would need the mod active, if that's what you mean.
No
If I figure out how to implement options like this for Zeus modules in the future, I may come back and update mods with options such as this, but at this time no plans are in place for this. Sorry.
@Era
Still no workaround for this, it's just a part of how the beam script functions.
I'm trying to think of a workaround for this, sorry for late reply