I want to say that on/off options on the website or SDK is one way to set restrictions in the world. Technically, it’s the same as using layers, colliders, or coding Udon to control the features (Dorones, Prints, etc).
If we agree that programmed restrictions (by layers, colliders, or codes) are acceptable to keep a good experience (for example, having a drone racing game as the author designed, even in private instances), then logically, the on/off settings should not be overridden by instance owners too, because the override might break things like the game mechanics.
Some might say: “More features, more fun. Let us use everything, even if it breaks stuff.” Okay, that’s a possible choice. But those restrictions are the world’s mechanics. You came to experience it as intended, right? Visiting a world is opt-in. You pick it; you get its rules. Don’t like it? Go to another world. There’s no need to force freedom here.
VRChat changed this now, instance owners can turn on features creators turned off. This breaks the world’s design, like smashing things the creator worked hard to build. It’s not just about mechanics; it’s disrespect to their effort. That drains their will to keep creating. And if creators quit creating, we all lose, players included.