Update comments for POI spawning

Vanilla commits:

1f89bcfb98

0defa2af1e

SQF/dayz_code/compile/fn_spawnObjects.sqf

@@ -7,8 +7,8 @@
 	
 	Notes for local spawned objects:
 	- Always present local objects are more performant than global, but less performant than town generator (spawning locally only when player is nearby)
-	- Recommend running on every machine including the server, so all units know about the object.
-	- Recommend running early during initialization, so units spawned on top do not fall through.
+	- Recommend running on every machine including the server, so all units know about the object and vehicles parked on top are not affected.
+	- Recommend running unscheduled before player_monitor.fsm and server_monitor.sqf, so units and vehicles spawned on top do not fall through.
 	- Not recommended for destructible or removable objects. Damage and deleted status are not synced across machines.
 	- Not recommended for objects with animations (like gates). Anim status is not synced across machines.
 	

SQF/dayz_code/init/variables.sqf

@@ -424,6 +424,9 @@ if(isNil "dayz_townGenerator") then {
 if(isNil "dayz_townGeneratorBlackList") then {
 	dayz_townGeneratorBlackList = []; // Town generator will not spawn junk within 150m of these positions.
 };
+if(isNil "dayz_enableFlies") then {
+	dayz_enableFlies = true; // Enable flies on dead bodies (negatively impacts FPS).
+};
 
 //Replace server individual settings with ranked settings
 if(isNil "dayz_presets") then { dayz_presets = "Vanilla"; };

SQF/dayz_code/system/mission/chernarus/poi/init.sqf

@@ -1,6 +1,6 @@
 /*
-	Add POI objects locally on each machine early.
-	Do not use execVM. This must be unscheduled so it finishes spawning before the player object is moved (possibly on top of them).
+	Add POI objects locally on every machine early.
+	Do not use execVM. This must be unscheduled to finish before player_monitor.fsm and server_monitor.sqf run. (objects or player spawn on top)
 */
 
 {