Yes, I get that part, like when I have AvatarTransform I need seperately animated body parts, like that’s the entire reason I was told to define a new “SetAnimation” that overrides the old ones specifically for the multiple parts, but that will come after I finish the animations for them, and I want to be careful about taking coding one step at a time.
Again, if you look at the API page I followed all the special rules it tells me for AvatarHiearchy specifically, as well as if you look at other parts of the code nearby, you will see they have the same exact rule/syntax I used for AvatarHiearchy, namely “class.property := value with matching type (like bool, int, etc)”,
and I defined AvatarHiearchy both in the actual viewport as well as the interface section of the code related to the viewport, again in the same exact way as everything else in the viewport is organized.
So therefore, I don’t think it’s because I haven’t added the parts yet, because with the way the error is phrased it will most likely tell me it “idents no member AvatarHiearchy” still, because that kind of error doesn’t care about whether I have it used elsewhere in the code or not, only about whether I defined it correctly (which I did to the best of my knowledge; it would be incredibly weird for it not to follow the same pattern literally everything else does in the viewport).