QUOTE(New Text Document)
5254B4 - deaths of 1516 for player 1 - Screen X position
5254B8 - deaths of 1516 for player 2 - Screen Y position
5254BC - deaths of 1516 for player 3
5254C0 - deaths of 1516 for player 4 - Screen Y position
5254C4 - deaths of 1516 for player 5 - Screen X position
Now the deaths for player 2 on one person's memory are different from the deaths for player 2 on another persons's memory.
So if you say:
Trigger: Player 1
Conditions: P4 has suffered at least 100 deaths of 1516
Actions: Create one marine at anywhere for P1
Then what whould happen, is that Player 2 would move his screen down, the conditions would be fuffiled, and a marine would be created on player 2's computer, but not player one's computer. Causing a de-sync.
However, it might detect the conditions locally, so the trigger might not fire becuase on player 2's computer it would check the deaths for P4 of 1516 and find that the conditions is met, then send the fact that the conditions is met to P1's computer, and then the actions would fire on both computers. In this case it would be compatable with multiplayer, however I think that it checks it on all computers, making it so there would be a desync.
Even if it doesn't desync, for other reasons it's impratical for multiplayer maps.