■ Summary

We have encountered a bug where a user is unable to join one of two worlds (created from the same Unity project but uploaded separately with different blueprint IDs), resulting in being returned to their home world.

■ Reproduction Steps and Behavior

Clear VRChat cache

Join the “Large Instance” → ✅ Success

Join the “Small Instance” → ✅ Success

Try rejoining the “Large Instance” → ❌ Fail (kicked to home world)

Rejoin “Small Instance” → ✅ Success

Pre-download the “Large Instance”, then join → ✅ Success

Try joining “Small Instance” → ❌ Fail (kicked to home world)

Pre-download the “Small Instance”, then join → ✅ Success

■ Analysis

Both instances are built from the exact same Unity project, with nearly identical assets and structure, but uploaded with different blueprint IDs.

It appears that VRChat client-side caching logic conflicts when dealing with such setups.

■ Workaround

Pre-downloading the instance via the “Download World” button allows the user to successfully enter the target world again.