|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001069||OpenClonk||Engine - C4Script||public||2014-04-22 18:29||2014-04-22 18:29|
|Target Version||Fixed in Version|
|Summary||0001069: Convert some player properties to team properties|
|Description||Team scenarios require many special rules like TeamAccount, TeamBaseMaterial and TeamKnowledge.|
I think it's unnecessery complication: Wealth, BaseMaterial and Knowledge should just generally be team properties.
The engine should make sure that every player has a team. The default should be one team per player in melee and one team for everyone in cooperative scenarios.
Callback functions like InitializeTeam and RemoveTeam could be introduced analogous to InitializePlayer and RemovePlayer.
Team melees would also profit from this, because team values like base material and wealth would be stored even if all members of a team have been eliminated and rejoin.
|Additional Information||In case you don't want to share gold with someone in a cooperative scenario (e.g. you're playing with a snobby newbie who wastes the gold), you can just pick a different team.|
One could even consider changing the "Owner" property of all objects to the team. However, because owners also control other player-related stuff, it might cause more trouble than it's worth.
|Tags||No tags attached.|
|2014-04-22 18:29||Sven2||New Issue|