can't find any workarround

here again:
after some more tests I found that the gameengine change player-side to "ENEMY" while dooing friendly fire... that is the reason why no trigger react to the player anymore after friendly fire.

for big missions you need a complex spawnsystem to keep fps. and with those spawnsystem all enviroment (enemys, squads, cars, civs, animals, ammoboxes etc.) arround the player will delete if the player disapear from the triggers.
So my squad cannot shoot back to my friendly fire, because they got deleted from spawnsystem a little bit faster after the gameengine changed my side to "ENEMY".

This player-side-change behavior on friendly fire should be changed. The engine should use an internal setfriend 0 or something like that, but please keep the playder-side.

workarround is to monitor player-side (while{true}) and change it back if player-side change to "ENEMY"...

(cannot edit the title from this issue)

workarround to prevent the player sidechange to sideEnemy:

player setUnitRank "COLONEL"; // = rating 7500
CountFriendlyDeath=0;
true spawn {

while{(true)} do { 
    waitUntil{sleep 0.3;rating player < 7000}; 
    CountFriendlyDeath=CountFriendlyDeath+1; 
    player setUnitRank "COLONEL"; //= rating 7500 
    hint ("HEY STOP! friendlyfirecounter: " + str CountFriendlyDeath); 
};

};

it is no bug, but this friendlyfire playersidechange behavior should be changed, to make missioncreating much easier.