Simply a result of Battlecraft logic.
If setting up a OS, you can choose the OSId it should belong to and the "team", initally thought to be used on map launch if somehow BF misses to read out the OSId in time. That would result in objects not appearing initially on first launch and perhaps requiring one "spawntime" to count down before the object appears the first time.
But during development the load engine was refined to always properly read out OSIds before placing the OS so it became redundant to define both OSId and setTeam, setTeam usually is used for objects independent from any flags and always spawning for the team set.
At least that's the explanation I picked up some years ago from some DICE guy in another forum...
_________________ Kampagne XI - Vereinte Achsenmächte
xFire: wgpsenshi
|