Open Beta

vrchat

hi

Follow-up to a closed bug report: [1860] "View Reports" button missing on Report QM page https://feedback.vrchat.com/open-beta/p/1860-view-reports-button-missing-on-report-qm-page This is a feature request to reintroduce a feature that was intentionally removed. In open-beta Build 1860 , the "View Reports" button was removed as an intentional change. However, this creates new issues: Users can no longer see which reports are open & closed. Users can no longer delete or "edit" open reports. The first issue removes any transparency and signal indications of actions taken by the moderation team. This may be intended for privacy considerations. In the past, personally these signal indicators have been a great source of education for myself about how the community guidelines are enforced by the moderation team. The second issue is greater. A report can be submitted once per category. If there is an error in the submitted report reason or the report itself, that report can no longer be deleted and/or resubmitted after deletion from the app. This "intended change" to remove the "View Reports" button is a regression that removes some of the incentives to use in-app reporting and may push people like myself back to web ticket reporting for tracking/editing moderation requests, which I think is less streamlined than in-app reporting and the opposite intention of the Trust & Safety Reporting Changes since January 2026.

Add delayed enable/disable support for Behaviour components VRCTween.DelayedSetActive was recently added, and I have found it very useful. I would like to request a similar shortcut for delayed changes to Behaviour.enabled . ## Background VRCTween already provides many convenient shortcut methods, including DelayedSetActive . It also has built-in tween support for components such as AudioSource and Image . These components inherit from Behaviour , so enabling or disabling them after a delay is a natural use case. Currently, if we want to enable or disable a Behaviour after a delay, we need to create custom wrapper logic in Udon. Having a built-in shortcut would make this pattern more concise and consistent with DelayedSetActive . ## Example Current approach: public Behaviour target; public void DisableLater() { SendCustomEventDelayedSeconds(nameof(DisableTarget), delay); } public void DisableTarget() { target.enabled = false; } Proposed: // Example only. VRCTween.DelayedSetEnabled(target, false, delay); ## Benefits * Consistent with DelayedSetActive * Useful for Behaviour components such as AudioSource , Image , and many others * Reduces boilerplate Udon code * Makes delayed enable/disable operations easier to read

When clicking on a category to report (such as stickers, prints, ect) it now asks if i want to close the report, even if i haven't selected something to report. Please remove this and reserve that for when you actually select something to report. Thankies!

This requests for the ability to make a public TweenEase variable to plug into VRCTween nodes. UdonGraph cannot make a variable of VRCTweenEase to expose as a inspector value. Having this would be useful for reusing a program and testing different ease types quickly. UdonSharp is able to do this already.

It would be nice to change allowing third person on desktop after the world is created, in the same way avatar scaling works. In my own game world I would like to enable third person in the lobby, but disable it when in game to avoid advantages.

With world preloading getting some nice UX improvements, it'd be a nice bonus if we could have a category list of worlds that are currently stored in the content cache.

I usually test my WIP worlds/updates by going into a public instance of one of my worlds and trying to gather as many people as possible to go to the WIP version. Being allowed to send an instance announcement would help tremendously even just in term of credibility alone, I do understand that it could undermine groups leadership so maybe restrict it to non group public/private instances of the world?

Avatar Performance Gating is a very useful tool for events and gatherings, but currently it appears to be limited to Group Instances. I would like to request that VRC+ users be allowed to enable Avatar Performance Gating when they host non-Group instances, such as Friends+, Friends, Invite+, or Invite instances. Many small gatherings are not organized through a Group. For example: casual friend gatherings small community meetups creator test sessions temporary events that do not need a permanent Group gatherings where the host wants some performance control, but does not want to manage Group roles or Group membership In these cases, creating a Group just to access Avatar Performance Gating feels like unnecessary overhead. The host may simply want to say, “please keep avatars within this performance level for this instance,” without turning the gathering into a formal Group event. This would also make sense as a VRC+ hosting feature. VRC+ users already receive instance-related benefits, and allowing them to apply Avatar Performance Gating to instances they personally host would give them a practical tool for improving comfort and performance for everyone attending. To avoid interfering with the existing Group Instance system, this could be limited in scope: only the instance creator / host can configure it only available while creating the instance, or through instance settings no role-based bypass system for non-Group instances no persistent configuration beyond that instance Group Instances can keep their more advanced role and permission controls This would not replace Group Instance moderation or event tools. It would simply provide a lightweight option for smaller, temporary, or friend-based gatherings where a full Group setup is unnecessary. Avatar performance issues can strongly affect comfort, especially in larger Friends+ instances. Giving VRC+ hosts a simple way to set avatar performance requirements would help reduce lag, improve accessibility for lower-end systems, and make small events easier to run responsibly.