A little more on this topic - essentially I need whitelist.

I want to have ALiVE persistence (logistics) to only save one specific item: "Land_Cargo20_red_F". I don't want it to save any other objects to the database. Just that one container.

Perhaps there is a way to do this by defining custom save data with ALIVE_fnc_setData?

Is there a way to tell ALiVE to ONLY save a specific item while blacklisting literally everything else?

@Tupolov

Hello,

I am getting some strange results when trying to save items inside boxes with player persistence and logistics enabled.

Oddly enough, it seems to work fine with only a few people. When we push the player count to 10+, it only appears to be retaining player data, no boxes or object positions.

I have attached my plugin log, any help would be greatly appreciated. This one has me scratching my head.

Download my log here

Been getting this error since 1.60 went live on some of the G.O.S. maps like Gunkizli and N'Ziwasogo. Any help would be appreciated.

http://i.imgur.com/NWEPotk.jpg

There have been several updates to the way AI is handled in Arma 3, and the ALiVE AI skill module lacks some of the new functionality and format.

For example, we now have "Suppression" and "Fleeing Coefficient" settings among others that are missing from the module. Might also be worth looking into that the format may have changed from actual numeric values (0.9, 0.5) to percents.

Seems there is also no way to change it across the board per faction as far as I know. Would be a great feature to expand because ALiVE already has a module for this specific reason.

Requesting the ability to delete SITREPS/SPOTREPS in a similar way to how we can CTRL+Right Click to delete Advanced Markers.

These tend to pile up on long persistence missions as players place them down quite often. In keeping with a milsim mentality, it would make sense that these could be deleted/cleaned up as needed. As of right now, maps can get extremely cluttered making it hard to track progress accurately.

In addition, we have discovered a bug when a high number of these have been placed down. It essentially stops putting the new SITREPS at the top of the list and starts putting them randomly in the middle/bottom of the list making it very difficult to find and read new ones that are being reported. I have to look at the ID on the marker, then scroll through every SITREP and find the matching ID to read it.

http://i.imgur.com/VZTgkIP.jpg -- If your map doesn't look like this... you are not operator enough!

Thanks for reading!

- Vegas

So, if you have any idea how to correct this, I am all ears! We don't want to lose our campaign progress, as we have been working on it for a few weeks now.

Appreciate the response.

Mission name also does not contain any special characters. It would not make sense to include periods in the filename that could cause issues, and like I said, it was working fine before 1.58 hit and we have made no alterations. Good suggestion though. Very confusing problem. =\

As far as I know, we do not have any special characters or characters/playable units with unique names. What is also strange, is that this is the exact same mission .pbo that we were using before 1.58 without issue. Of course after the latest ALiVE update I replaced all the modules, but other than that it is unchanged.

I will scrub through our mission and framework again tonight and double check that I am not missing anything. Appreciate the response.