Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
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