I want to expand my flowlab knowledge today, so can someone give me the laydown of how flowlab parents and children objects work? I know some of the basics. You make a parent object… parent object code clones to the children… but I kinda need some specifics, as every coding program’s parenting is different.
1 Like
A child, is an object that has its own code along with its parents code.
So, for example… I’m using a parent in my game Fauxport. I’m using a base object that has rotations, so I can set other objects in my game as a child for that parent. Now, even if the parent isn’t place in game the children still run the rotation code. It works well because you can have base code in one object that you don’t have to copy and paste into every object.
For example, I COULD make an enemy parent. Now every single enemy design I have will be a child of this parent… making it easier to make new enemies.
AND THEN, there’s grandparents… parents follow grandparents code and children follow parents code. So if you want to really make a huge project grandparents are pretty cool.
If you’re making COD there might be some great grandparents 
2 Likes
Also, forgot to mention… all children follow the parents properties. So if a parent is not solid the child won’t be solid either.
I do believe I’m correct, if anyone else knows correct me but I think that’s how it goes.
2 Likes
It’s just behaviors iirc, other properties are still unique
2 Likes
Alright, thanks for clarifying I didn’t know if I was right or not.
2 Likes