Launching into a world with a max capacity of 0 crashes the VRChat client
tracked
WubTheCaptain
If you try to launch a world that's not meant to be joinable due the world's maximum players being set to 0 (or other reason with this specific world), the VRChat client will hard crash in a specific scenario when trying to send the user back to their home world.
Affected world: by Phantom Touch (
wrld_07b20a52-c0b5-4659-85ac-a855fc11cb7e
) https://vrchat.com/home/world/wrld_07b20a52-c0b5-4659-85ac-a855fc11cb7e/infoTrying to drop a portal or join this world from in-app fails with an error message, stating it's full. Creating a new instance in-app and then dropping that portal works, however anyone entering the dropped portal will be sent back to their home world once the world is initialized.
Another quirk: Being invited to the above world says "join them" instead of "join them in [worldname]".
The specific crash trigger is caused by launching VRChat client from an invite/launch URL or from Steam launch parameters.
Steps to reproduce the crash:
- Close the VRChat client.
- Launch VRChat from the following URL: https://vrchat.com/home/launch?worldId=wrld_07b20a52-c0b5-4659-85ac-a855fc11cb7e&instanceId=BUGREPORT - alternatively set the VRChat launch parameters in Steam to vrchat://launch?id=wrld_07b20a52-c0b5-4659-85ac-a855fc11cb7e
- Wait for the world to download and initialize.
- Crash.
Expected behavior: I anticipated to be sent back to my home world, or fail graciously in some way. Error world in the worst case scenario.
Actual behavior: The VRChat Steam client crashes after loading into the world. A single frame is displayed from the world before the crash.
Reported-by: dronenight
Photo Viewer
View photos in a modal
Log In
This post was marked as
tracked
_
_tau_
updated the status to
complete
This has been fixed on the server side by not allowing worlds to have a capacity or recommendedCapacity lower than 1.
WubTheCaptain
_tau_ Apparently max capacity 0 wasn't the bug trigger here, I can still launch to that world (which now has a max capacity of 1) with
vrchat://launch?id=wrld_07b20a52-c0b5-4659-85ac-a855fc11cb7e
and hard crash the client.Oddly enough, the BUGREPORT instance reports as 0/1 people in it, but also errors out as "full":
2026.05.20 02:40:01 Error - [Behaviour] Could not enter room because: Instance is full․ (You are not allowed to travel to that location. Instance is full․ (Code: 403))
2026.05.20 02:40:01 Warning - [Behaviour] Failed to join instance 'wrld_07b20a52-c0b5-4659-85ac-a855fc11cb7e:BUGREPORT' due to 'You are not allowed to travel to that location. Instance is full․ (Code: 403)'
All this fix did was make it easier to join and create new instances of this crash inducing world.
WubTheCaptain
_tau_ The server is also reporting the BUGREPORT instance above to have both 0/0 and 0/1 max capacity on launch.
WubTheCaptain
_tau_ I also tried launching into a newly created instance with instanceId=BUGREPORT2 and launching into it. The new instance reports 0/1 and being full too.
Essentially, these worlds are still treated as capacity or recommendedCapacity 0, but the reported max capacity or recommendedCapacity is a lie.
Photo Viewer
View photos in a modal
_
_tau_
WubTheCaptain: Old instances will stick around and remain broken, yes, but new instances should no longer cause a crash. At least in our testing it was no longer possible to create a new instance of any world that triggers the crash behaviour.
This post was marked as
available in future release
StormRel
updated the status to
tracked
WubTheCaptain
It seems no crash dump is generated from this on my end.