You can use symolic links for this, from documents folder in powershell:

New-Item -ItemType SymbolicLink -Target '.\Arma 3\missions\' -Path '.\Arma 3 - Other Profiles\ProfileName\missions'

In T175509#2500188, @Leopard20 wrote:

Set shadow distance to any large number (500m, 1km or above)

Shadows were never meant to be set above 200m

But we are here - last update allows it without scripting. also, this does not negate the fact that this happens at 200 meters, just that further increases intensify it more and this becomes noticeable even on powerful hardware.
also, this does not negate the fact that this happens at 200 meters, it’s just that further increases intensify it more and more and this becomes noticeable on powerful hardware
it would be great to fix this since the A3 really lacks shadows at long distances

diag_captureFrame results:
on - shadows at extreme preset
off - shadows disabled
*m - shadow distance
other settings: maxed out, 1440p (100%), 3km total + objects view distance

To make it clearer and more useful I rewritten this part of proposal with more explanations.

To avoid braking of backward compatibility
we can introduce new commands with slightly
different name, but same behaviour as normal
counterparts, except for hasmaps:

a = [1, missionNamespace, uiNamespace, 4];
b = [] + a;
//a = [1, missionNamespace, uiNamespace, 4]
//b = [1, missionNamespace, uiNamespace, 4]

It works fine

In T119610#1495529, @danjoo wrote:

Oh i see.
So how do you distinguish between an Opfor player and A Blufor player when executing code on them when they are dead. Using civilian would still apply the code to both, when you only wish to target one

If object is dead then his side == CIVILIAN
playerSide can help you

Launched publisher v1.5

This bug working for MP: Run editor >> setArepture value >> join on server with night mission >> you have legal cheat :D