I'm working on a realtime multiplayer game project.
There are entities like Player, Game, Flag etc.
And bunch of it's behaviours like
PlayerRespawnBehaviour, PlayerWalkBehaviour, PlayerLifeBehaviour, GameGoalBehaviour
Over 60 behaviours...
However it's get to level that very hard to break new features into part and let another developer handle the development without know every each behaviours doing.
So I currently consider adopt DDD. Take parts of DDD technique by separate the concern of game features instead of domains? (without having much layers, mutiple machines as DDD)
I'm sure there will be lot of sub-domains which will separate by each feature.
Goals here are
- Prevent behaviour references each others in the bad ways.
- Introduce new features to new developer who just jump in.
But I'm not sure that it'll cause problem if I do need too much numbers of integration between sub-modules.
So is it a good practices?
Does any one experiences this pro & cons?