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
Basically what's happened is that mod update introduced compatibility for RA base building codelocks, and for the setup I am using on our server (we use RA for upkeep, BBP for building, expansion for it's codelock, and bridge for those to work on BBP), that causes a multiple declaration of function error due to the defines.c in your mod including #define codelock. I don't know how to override that other than by repacking with #define codelock removed. Given that I doubt you would want to update your mod for niche setup like ours, I was wondering if you would permit a repack in these circumstances?
"Can't compile "Game" script module!"
CL2ECL_Bridge/SScrripts/3_Game/const.c(1): Unknown type 'LB_Master_Game'
Steam downloads it and the content folder populates with 2789443787, but the mod isn't listed in DayZ or DZSA Launcher and no folder (junction point) is created in the DayZ client !Workshop folder...
Any ideas?