foundrey
NNormal
•Created by foundrey on 5/27/2025 in #🤝ask-a-question
Confusing MetaModel Ownership Situation
Makes a lot of sense in hindsight..
I was looking at normcore's ownership system as an "affirmative" system (i.e. it allows players to do things) as opposed to a "negative" system (it denies players from doing things).
Guess I was stuck in a more traditional distributed authority mindset tbh hahaha but appreciate the clarification!
If you guys want any feedback on the docs, my suggestion would be making that fundamental difference more spelled out. Me and the guys on our team were definitely scratching our heads wondering, but tbh also could have just been on us misinterpreting.
12 replies
NNormal
•Created by foundrey on 5/27/2025 in #🤝ask-a-question
Confusing MetaModel Ownership Situation
So I shouldn't expect to have the ability to make changes to models nested under a parent view that is owned by someone else.
That makes sense. I've seen in the docs that it's often recommended the root view is left unowned when a realtimeTransform with physics is also used on the root so I can do that, and in that case I assume I'd have no problem pushing updates to the child views because nobody owns the parent?
12 replies
NNormal
•Created by foundrey on 5/27/2025 in #🤝ask-a-question
Confusing MetaModel Ownership Situation
So the hierarchical ownership enforcement makes sense and I've seen that in the docs (though admittedly sometimes the normcore AI suggests that I can make edits to a MetaModel even if the parent is owned and sites the same lines in the docs), I guess in that case I'm just confused what the ownership purpose of MetaModels is in that case..
is it just persistence? so that you can log back in and keep owning the same thing? the collaboration example doesn't make sense to me so I'm struggling a bit with it 😅
12 replies