state object linkage in player hierarchy? the same between v2 and v3?

D

DankP3

Active member
My recollection of v2 was that I could place a StateBehavior on any player child object (even deep in the hierarchy) and it would react to the player states.
In v3, it now only seems to work if on either the root, or 'player' objects. On any other child transform and the states do not activate.

Is this intended? and if so, do i need to link gameobjects to the player object as and when i want to use the state system on deep children? (or put the StateBehaviours on a root object and have them look for their target gameObjects)

EDIT, now I think more, I am not sure states were activating on the capsule collider which would suggest a bug.

Thanks,
 
Last edited:
The state system did undergo some changes in v3 but the not auto linking to child objects was unintentional. This does look like it's causing some problems as you mentioned with the capsule collider. I'll restore that functionality in 3.0.2
 
You must log in or register to reply here.
Top