Demotivating it has already accomplished. I’ve put all my WIP world projects on indefinite hold until VRChat changes this.
“VRChat is cold to the requests of world authors” is an understatement. I sometimes feel like they downright hate us.
Edit: To avoid this reply not adding anything to the discussion, I would like to point out that there are legitimate concerns with not respecting world creator’s disabled content settings. The drone is already proving itself to be troublesome at best with it’s ability to collide with the world and game objects. In addition, the drone itself could be used to violate privacy, something that was not an issue with the flying camera. Prints are their own disaster- I really don’t like how they stick around forever until a player leaves the instance. It leads to a lot of clutter, not to mention the questionable things users have displayed as prints.
And when are we getting world physbones? This canny is coming up on 3 years old. While unrelated to the current issue at hand, it’s something I feel like I should bring up, as it’s a perfect example of VRChat’s neglect of world creators. (Another edit: VRC Constraints also don’t work in worlds, another feature solely for avatars) I don’t like the current strategy of the World SDK being drip fed updates from the Avatars SDK. I’m definitely looking forward to Steam Audio, only so we can drop the unmentionably awful VRC Spatial Audio Source component that has been plaguing us for too long. New, big features are nice, waiting sucks- it would be nice for some improvement on what we have while we wait for bigger updates, (that may or may not come) like Soba.
Fortunately, while I feel that VRChat won’t do anything about this clear issue they’ve created, the community is not helpless- remember Booping? I’m glad we got that dropped before it became an issue. This, like Booping, is still an Open Beta feature and can, and hopefully will, be changed before it is fully released.