World/Udon Bugs & Feature Requests

Allow world creators the ability to moderate their OWN worlds and issue their OWN bans. I'm tired of seeing crashers and exploiters in my worlds and kicking them is nothing. I want the ability to ban certain individuals from my worlds. There is absolutely no harm in doing this. Who is it going to hurt? The exploiters and cheaters. What if world creators abuse it and ban people from THEIR OWN worlds? Well it's their fault their world fails to gather a population. What else will this do? Allow world creators to suit the needs of their wanted audience. it will also help take the stress off of the actually game moderators. Thank you, Lucifer MStar - Creator of 30+ worlds including church of marriages. P.S. Communicate more with your community on what you are doing about these crashers and exploiters and maybe the heat and stress will die down. Honestly this is the most annoying thing communication.

It'd be helpful for world creators to know how many people are entering their world as well as how often users are coming back.

Issue: Currently it's not possible to react to a players voice at all. We don't know when someone is talking or how loud they are for example. This limits us from making games where someone needs to be quiet to hide from an enemy for example. For security reasons it makes sense that we can't just listen to a player voice, which is why I think only giving limited access to it would be fine. Suggestion: Add an isTalking bool to the VRC Player API which is true when voice is detected and false when not. Add a loudness float to the VRC Player API which is a value between 0 and 1 depending on how loud a player is. (Basically how the current Voice parameter works on Avatars) Add a viseme integer to the VRC Player API which would indicate what viseme is currently used. (Basically how the current Viseme parameter works on Avatars) These would allow world creators to integrate player voice into game play while also not just directly giving them access to player voices for security.

Knowing the Photon ID of an UdonBehaviour would allow us to troubleshoot sync between Quest and PC by providing ingame UI displaying the ID of certain scripts. Non-matching Photon IDs is one of the most painful issues when maintaining Quest support, especially since some Quest worlds rely on a different project/hierarchy which can bring Photon IDs out of sync. Networking doesn't work and it's really hard to debug or find out why.

Spline editor and components is one of most exciting new feature for Unity 2022. Now our project has been migrated to 2022, So we are ready to use it! Please expose those components for world creation and Udon VM: ・Spline ・SplineAnimate ・SplineExtrude ・SplineInstantiate It would be better if the Spline package is automatically added to the project when the SDK is imported so that these features are easily accessible.

This was reported as fixed in 2024.4.1p3 but it looks like the problem crept back in and exists in SDK 3.8.2 / 2025.3.1 (haven't tested any other versions). Since the previous canny was closed out as complete, thought I'd open a new one. Prior bug report on this issue: https://feedback.vrchat.com/udon/p/braces-inside-strings-in-vrcjson-can-fail-to-deserialize // This works if(VRCJson.TryDeserializeFromJson("\"{\"data\":\"test\"}", out DataToken token2)) Debug.LogError("Failed to deserialize JSON"); else Debug.Log("Successfully deserialized JSON"); // This fails. Only difference is the braces after the word test in the JSON string. Number of braces or their configuration doesn't seem to make a difference. if(VRCJson.TryDeserializeFromJson("{\"data\":\"test{}\"}", out DataToken token1)) Debug.LogError("Failed to deserialize JSON"); else Debug.Log("Successfully deserialized JSON"); Thanks! -Tea

At present, PhysBone is not supported in the World SDK, so Dynamic Bone must be used to implement physics-based animations. However, the version of Dynamic Bone used in VRChat is already quite outdated—likely version 1.2.1, whereas the latest available version is 1.3.4. The contents of the Dynamic Bone component included in the component whitelist have also changed, with new parameters such as "Roots" and "Blend Weight" being added. Naturally, these parameters that do not exist in the older version do not function in VRChat. On the Asset Store, only the latest version of Dynamic Bone can be downloaded. The discrepancy between the available version and the version used in VRChat could lead to confusion when setting up worlds, especially since the version of Dynamic Bone used in VRChat is not documented anywhere. To test with the same version as VRChat, we now have no choice but to transfer an older version of Dynamic Bone that was downloaded when that version was still available. If the World SDK plans to continue using Dynamic Bone in the future, I strongly urge that the version of Dynamic Bone used in VRChat be kept up to date. --- 現在のVRChatランタイムで使用されているDynamic Boneのバージョンは既にダウンロード不可能です。 現在、WorldSDKではPhysBoneがサポートされていないので、揺れものの実装にはDynamicBoneを使用する必要があります。しかし、VRChatのランタイムで使用されているDynamicBoneは既にかなり古く、おそらく1.2.1だと思われますが現在の最新バージョンは1.3.4です。コンポーネントホワイトリストに含まれている、DynamicBoneコンポーネントの内容も変化しており、例えばRootsというパラメーターやBlend Weightというパラメーターが新たに追加されています。これらの古いバージョンにないパラメーターは当然VRChat上では動作しません。 アセットストアではDynamic Boneは最新バージョンしかダウンロードすることができません。利用可能なバージョンと動作バージョンの違いはワールドをセットアップする上で混乱のもとになるでしょう。VRChat上でのDynamicBoneのバージョンがどこにも明記されていないからなおさらです。私たちが現状でVRChatと同じバージョンのDynamicBoneで検証するには、そのバージョンがリリースされていた当時にダウンロードしていた古いバージョンのDynamic Boneを移植する以外に方法がなくなりました。 今後もワールドSDKではDynamicBoneを使い続ける予定であるのであれば、せめてVRChatのDynamicBoneのバージョンを最新に保っていただきたいです。

There is an undocumented limit on Network IDs. If you assign a Network ID beyond 10 000 to a PlayerObject its persistence features will break while the UdonBehaviour itself still functions and syncs. ClientSim throws the following error: ran out of player persistence view ids In-game testing results in Removed some Player Persistence metadata that had invalid IDs. errors. Apparently there is a limit of 100 000 for Network IDs in general, its way less likely to hit this, but this also seems undocumented. The difference in limit for PlayerObjects and standard UdonBehaviour objects is confusing and the provided errors don't accurately explain how to solve this issue. The Network ID Utility also does not seem to take this limit for Player Objects into account and does not warn or ensure a lower ID is assigned to the persistent objects. Furthermore, the Network ID Utility crashes on projects with this many Network IDs, but this was already documented here: https://feedback.vrchat.com/sdk-bug-reports/p/network-id-utility-has-massive-performance-issues

Fairly simple request. Half of what makes Contacts what they are is currently missing. We can only contact from Avatar to World to trigger something in the World. What we need is the ability to send parameters from World to Avatar to trigger effects on the Avatar. An example of this would be a weather system. You stand inside a contact for rain and it will send a inRain parameter to the Avatar which then can implement something in their animator layer to do something with this, such as enabling shader effects to look rained upon or wet. This could be used for many effects, sandy in the desert, muddy in swamp, wet in rain/water, damaged/bloody in games with health and so on. Allowing communication from the World to an Avatar would open up endlessly more ways to interact with the World in a variety of ways.

Checking the equality/inequality of a system-defined enum with equality/inequality operators ( == / != ) will fail. As a result, this example codes in the document don't work as expected: https://creators.vrchat.com/platforms/android/android-best-practices/#2-detect-mobile-players-in-your-world-automatically public override void OnInputMethodChanged(VRCInputMethod inputMethod) { if (inputMethod == VRCInputMethod.Touch) { // Run code for touch input } else { // Run code for non-touch input } } (The UdonGraph version (attached image) also has an identical issue.) Workaround Cast to underlying values and compare them. if ((int)inputMethod == (int)VRCInputMethod.Touch) Analysis UdonSharp compiles the expression inputMethod == VRCInputMethod.Touch into EXTERN, "SystemObject.__Equals__SystemObject__SystemBoolean" Although Object.Equals(Object) is overridden by Enum.Equals(Object) , which the inputMethod may have, with comparing underlying value, this EXTERN seems to call the Object.Equals directly (maybe via reflection API), and it returns the unexpected result (by only comparing the referencing instances). The EXTERN, "SystemObject.__Equals__ comes from here https://github.com/vrchat-community/UdonSharp/blob/22307065bd408dfd163fe46b0b8b701a4efcbc00/Packages/com.vrchat.UdonSharp/Editor/Compiler/Binder/BoundNodes/BoundInvocationExpression.cs#L420 And replacing the System_Object of this line with System_Enum doesn't work because the Enum.Equals is not exposed. Suggestions Temporary, rewrite the example codes using cast operator Expose System.Enum.Equals And replace the EXTERN with System.Enum.Equals