Quantcast
Channel: Questions in topic: "parenting"
Viewing all articles
Browse latest Browse all 302

When and why to put object as child of another?

$
0
0
I am an amateur game developer, lets get that said first and foremost. As I have been working on my game for a few months now, I am starting to face to some design decisions in regards to how I should structure my game objects in the scene hierarchy. Right now I place them where I think it makes sense: - I have a empty game object that has children that are the managers and systems. - I have a terrain with the terrain elements (rocks, trees, grass, etc) as children of the terrain they are part of. - I have a character spawner that is placed .... well, not quite sure yet. Hence the question. Are there a set of inherent rules when it comes to deciding what should be a parent or child of something else. I figure it mainly matters in regards to position and rotation but I cant think of any other reason why other than simply organizing. I presume if everything was on the same level then the game could still function than if it were well organized with an actual hierarchy. When should I child an object and why, or why not?

Viewing all articles
Browse latest Browse all 302

Trending Articles