Установить 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 (вьетнамский)
Українська (украинский)
Сообщить о проблеме с переводом
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.