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
Not to imply this comes with strings attached. Whether or not you add content for that is totally up to you. Changing the scope would definitely make the vehicle available, or in my case, I changed a line of data manually in my mission file to make it available and then saved it in a composition for later use.
I'm sure there's plenty of other hidden things in the DLCs.
in your expEden.pbo/scripts/config.cpp you are doing this "samples[]+="
Which does NOT work, and causes RPT spam "Config array append with unsupported value type"
The += operator can only append numbers and strings. It cannot append arrays.
That is an engine limitation that should be fixed, but considering your current code doesn't even work, you can probably just delete that as it currently does nothing besides spamming errors to RPT.
Also your PBO naming and prefixes violate convention.
The "a3/" pbo prefix, is for base game Arma 3 files, mods shouldn't be putting themselves into there.
Same applies to the CfgPatches (and pbo filename) "_F" suffix.
@Shank нere are the mod files you need to paste & replace in this path, ambient cats and dogs will be silent:
C:\Program Files (x86)\Steam\steamapps\common\Arma 3\!Workshop\@O&T Expansion Eden\addons\