In T160224#2225214, @BIS_fnc_KK wrote:

rev 148073

Also, what you are doing makes no sense, I mean saving mission config in profile namespace, same as saving display for use later. Mission config exists only while mission is running. New mission, new config instance. On top profile namespace is serialized and loaded on game start. way before any mission is started, so mission config saved to profile namespace will give you exactly nothing after you left mission.

This ticket does not actually show the crash which I experienced because I was unable reproduce it in a new mission. Instead it shows how testVar failes to load from "cfgTestSave" and is null. Trying to use this null variable probably is what lead to crash

The array version of this command seems to be buggy

Any update on this? It's really bad when you want host a server and go to the mission select screen then arma will immediately crash. People are probably thinking what is causing their arma to crash when it's include dependency in a mission file

I think the bug lies in inRangeOfArtillery because it returns true even when artillery cannot fire because of being too close to the target.

if you put the artillery really close to target (less than 100 meters) then inRangeOfArtillery will return false.

Put this in init.sqf for testing:
player sidechat format["inrange: %1", getMarkerPos "target" inRangeOfArtillery [[_artillery], "32Rnd_155mm_Mo_shells"] ];