-well dont know if this helps, but in my case it was a player with an unusual character in his name (ü), might be something like that..

FIXED IT!!! after, what seems, a million hours! one of our players used an umlaut (ü) in his name, persistence apparently did not like that! :-)

thanks for the reply! :-) i guess ill just have to accept that persistence is not possible on my end.

will editing a mission which is already saved to the warroom break its persistence i.e. player and ai location?

okay did that, but now only player logistics persists, really scratching my head! :-)

the question still stands... am i not only supposed to put the alive.cfg in the arma3 root folder, or should it be in the same folder as the server config file?

Wait a minute what -config param? btw persistence broke again...

Solved it! :-) it seems that if you do not use the standard steam location for the arma3 folder, you have to place the alive.cfg in users/name/appdata/local/ALiVE can anybody confirm this?

i am using the bis respawn..
http://pastebin.com/R58ZK1kn

certanly: "-mod=@CBA_A3;@AliveServer;@ALiVE;@ASDG_JR;@BC-Phoenix;@hlcmods;@hummwv;@JSRS2.2;@zooloo75;@R3F_ARMES;_CommonRedist;Curator;Launcher;@BPX_UTS15;@Improved_Ragdoll_Physics
it only happens after a couple of deaths sometimes 2, sometimes 3... any ideas?