(MP) issues ARMA3 v. 1.6

[whiztler 137]

I was wondering if people have come across issues with v1.6. F.i. I noticed that the ID numbers of Altis have changed. This took me a while to figure this out.

Biggest issue I have come across is that Triggers sometimes work and sometime don't. E.g.:

IED trigger:

Activation: Bluefor, Present

On Act.: bomb="M_Mo_82mm_AT_LG" createVehicle (getPos ied1); deletevehicle ied1;

ied1 = garbage

Tested on a dedicated server. Issue does not occus with local testing.

[MulleDK19 21]

The IDs change every time the map is altered. Don't rely on IDs in your missions.

[meatball 25]

Yeah, it's been doing that since Alpha. For some crazy reason the ID's numbers of static objects on the map change every patch. Best way to deal with it is to set up Gamelogic objects near items you want to watch setting up a variable/object name for that object with nearestObject. Then set another trigger to fire based on the status of that variable/object name.

This also means that grouping a trigger with a static map object will break every time there's a patch b/c when you do that, it's groups to the ID, not the object.