Installa Steam
Accedi
|
Lingua
简体中文 (cinese semplificato)
繁體中文 (cinese tradizionale)
日本語 (giapponese)
한국어 (coreano)
ไทย (tailandese)
Български (bulgaro)
Čeština (ceco)
Dansk (danese)
Deutsch (tedesco)
English (inglese)
Español - España (spagnolo - Spagna)
Español - Latinoamérica (spagnolo dell'America Latina)
Ελληνικά (greco)
Français (francese)
Indonesiano
Magyar (ungherese)
Nederlands (olandese)
Norsk (norvegese)
Polski (polacco)
Português (portoghese - Portogallo)
Português - Brasil (portoghese brasiliano)
Română (rumeno)
Русский (russo)
Suomi (finlandese)
Svenska (svedese)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraino)
Segnala un problema nella traduzione
Thanks!
0:34:45 Error in expression <true];
for "_i" from 0 to 5 do {_flamer setObjectMaterialGlobal [_i,_flamer setO>
0:34:45 Error position: <setObjectMaterialGlobal [_i,_flamer setO>
0:34:45 Error Type Any, expected String
0:34:45 File Root_Anomalies\Root_Flamer\AL_flamer\flamer_main.sqf..., line 22
However, I will add in an additional switch, that, when enabled, will override the minimum 200 meter distance in the next update.
Thanks for taking time to solve it
If I can make a suggestion I would allow to have a smaller (minimum slider) area for the anomalies (50-100 metres instead of 200) if it doesn't create issues or is difficult to do
A common issue I've found so far is that when updating this mod using a MSP (Managed Service Provider, like webconsole and custom webpage), the mod often fails to get updated properly. I would suggest uninstalling my mods and reinstalling them again and forcing a repair if possible (on both Server and Client) and boot the server. This seems to fix the issue for most people.