you got a bug report for me to upvote?
Well VRC Is on iPhone and android, both can’t run VR . I am aware there aren’t as many of vrc mac users but still, it would be so great to see.
Yes! I promise you 100% I will come dev in VRChat if we get Soba. Cheers to 2026 by the way. 
I think the best way to encourage VRChat to do things is to link feature requests in these threads, so anyone interested can updoot, so they can see the amount of clicks from this very thread.
But either way, for something like VRChat on macOS, I think they’re going to be more focused on how much work they’d have to do to get VRChat running. If they can use compiled iOS shaders, then that is a good path, but if they have to add macOS as another platform for worlds to be uploaded, then its not going to happen any time soon. I haven’t gotten around to uploading anything for iOS yet.
1 Like
I believe the reporting mechanism should ideally replicate the network parameters and object states of everyone involved. Furthermore, it should include backups of the objects themselves, such as avatars and worlds. This should be based on synchronously retrievable states rather than recordings.
The reason for this isn’t just that AI can create deepfakes, but because it has been observed that the environment harbors numerous malicious modifications and total bypasses of EAC (specifically referring to EOS). Highjacking/tampering with the client to forge content is far more stable and reliable than AI forgery. I have discovered the existence of certain tools that can achieve this effect. (I apologize that I cannot disclose or report this publicly, as it might alert too many individuals.)
Makes sense, any furry that doesn’t wear clothing is basically considered pornographic for moderation purposes.
So can we finally get an update to the Creator Guidelines and Community Guidelines to clarify what constitutes “sexual content”?
Since apparently, uploading any kind of texture or mesh that may contain NSFW elements, no matter if visible or not, constitutes a breach of TOS and Community Guidelines for sexual content and will result in a ban if caught by moderation?
Visible or not can be very subjective, I’ve seen a magnifying glass asset that as a quirk of how unity renders things, can make anything on the same render queue invisible. Sometimes it’s just clothing, more amusingly it’s the clothing and body, so I just saw some accessories. On my own Avatar I have a demo setup such that I can show people a look through a panel that hides my hair.
I also had one situation where someone’s clothing was on a render queue at or above 2500, and so the clothing was invisible to a wire frame view type shader, but not the body.
So get out a hammer and pound the nipples flat on the sfw model I guess.
1 Like
If you have an avatar with “NSFW” geometry or textures then yes, you are taking a risk by using it – especially in public, or in spaces it could be reasonably reported. To be clear, this is not a new policy – it has always been this way.
This is more or less what I said in the quoted post on Reddit, but to clarify even more:
If those textures or geometry are present on your avatar, then it’s reasonable that they could be exposed – intentionally or otherwise. That could mean Shader Magic 
, complex animation logic, toggles, or a billion other things.
I can understand that this is frustrating because many folks don’t look at their avatar in that much detail before they hit upload, but ultimately, you’re responsible for the content you upload.
If you feel that you’ve been wrongfully banned, however, you’re more than welcome to submit an appeal!
1 Like
Please followup with a Dev announcement when the T&S Helpdesk resumes actually reading tickets which contain the requested ‘additional evidence’, instead of automatic closure and the ‘we encourage utilizing VRChat’s In-app reporting system’ boilerplate.
Please consider Setting all Content Filtering options on as default, in an interim easy toggle now. I know age/content hard gating is in development, I am excited and can’t wait for it! Set all Content Filtering options on as default | Voters | VRChat. I know the system was disabled because content creators were overtagging with this system in the early days, and I know this system is not yet tied to verified age, but please please turn it on by default. So many people don’t know it exists. It allows people who tag their avatars correctly to not display to those that choose to not see certain kinds of content in the game. This could prevent all users from seeing content they don’t want to, and actively choose to consent to seeing language/gore/adult themes.
I dislike the hypothetical situation where someone can join a private event, with the group/event having clearly defined rules and description, in an age verified 18+ instance, but ANY one Individual could still technically not “consent” to seeing certain content, and potentially report it.
If this older content filtering was on by default, the potentially offended user would have had to ACTIVELY choose to turn off certain content filtering, they at that point consented.
From the 12/18/25 Post:
This would serve the purpose of gathering consent. In those cases, you should also run that instance or event as an 18+ Verified Group instance. As always, use your own best judgment – it is your responsibility to ensure that attendees know what they are walking into, and you should employ every tool available to let them know, and fulfill that responsibility.
I will and have been as a group admin using all these tools, and will be diligent in doing so continuing on. But I see this being one more “every tool available” that we can use to gain active conscious consent.
1 Like
Why can’t you put this in your Creator Guidelines or your Community Guidelines?
Something I’ve been thinking about is in one of the previous updates VRChat allows the face mirror to output to Spout. I wonder if it’d be at all possible to whitelist KlakSpout in the VRChat Avatars SDK for those of us that don’t want the camera to be following the head all the time, or at least offer some Spout support within the SDK for either us streamers or for OSC purposes? I made the request on the feedback board here if anyone else is interested
Because then they are legally liable, since it creates more of a legal greyzone. That’s why the most they say these days is, “Keep private things private”, while their ToS still explicitly bans NSFW content.
This is the best solution, because yes, if you happen to be in situations where you have NSFW assets and you are worried about who can see them and when, you should consider:
- Not being around those people and finding new friends
- Making versions of your avatars that are SFW for public/populated instances
1 Like
I have a question, why is the amount of avatars able to be favorited 50 for non vrc+ users? Is it a storage issue? I also have a suggestion: for quest players increase worlds able to be downloaded from 100 megabytes to 200, but make it so there are instances with only 1/2 of the players allowed as the original world. Make these named quest instances, make it so anyone can join this type of world and don’t allow quest players to go to worlds over 100 megabytes with the original amount of players allowed. This way, quest players can still enjoy bigger worlds without killing performance.
When I first started using vrchat I didn’t really have a chosen avatar so I made great use of the favorites, and found some ways around the limitations, like there is a world where you can paste in a comma separated list of avatar IDs and browse through them. Also more recently with persistent data you can favorite avatars in prismics avatar search.
On one hand the limited slots is annoying, but I can think of many many other ways they could be more annoying in encouraging people to get vrc+. These days I guess I do have 50 favorited.
One work around I used to see is that sometimes people would make their own little world just for holding some avatar stands.
For the world size limit on quest, every time I see that request submitted to the feedback site I leave a comment basically stating that vrchat actually works on the quest 3 these days and to please change nothing until the quest 3 is EOL. With the string loading feature, the size limitation is able to be worked around. Base64 encode an astc compressed texture or whatever you want.
The smaller user limit would be interesting to see implemented as the user limit would need to apply cross platform. But yeah go post to, feedback.vrchat.com unless you have already. But I think they’re putting off saying anything until they EOL the quest 2.
Actually vrchat please be firm on EOL for quest 2, don’t be coy about saying that the builds are untested or whatever, just say it’s EOL whenever you feel like it.
1 Like
Cool.
This topic was automatically closed after 14 days. New replies are no longer allowed.