[Feature Request] Create instance dialog display name #324

Closed
opened 2026-04-05 16:17:36 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @TapGhoul on 9/10/2025

Explain in detail what your suggested feature would be used for.
Creating instances with display names with the new API

Describe how it would look if it requires a UI.
An additional field below "World ID" in the "Normal" create instance flow

Explain why people would want to use it.
VRChat has exposed a "displayName" field you can post to create a new instance, and is able to be set in the VRChat client (default set to "'s Instance", and has history)
It would be handy to have the field be settable from within the UI.

See https://vrchat.community/openapi/create-instance - "displayName" field POST value.
If left empty, the displayName field should be excluded from the POST body, resulting in the standard randomized ID generation.
The client's length limit is 32 characters. I don't know if the API restricts similarly.

*Originally created by @TapGhoul on 9/10/2025* **Explain in detail what your suggested feature would be used for.** Creating instances with display names with the new API **Describe how it would look if it requires a UI.** An additional field below "World ID" in the "Normal" create instance flow **Explain why people would want to use it.** VRChat has exposed a "displayName" field you can post to create a new instance, and is able to be set in the VRChat client (default set to "<DisplayName>'s Instance", and has history) It would be handy to have the field be settable from within the UI. See https://vrchat.community/openapi/create-instance - "displayName" field POST value. If left empty, the displayName field should be excluded from the POST body, resulting in the standard randomized ID generation. The client's length limit is 32 characters. I don't know if the API restricts similarly.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/VRCX#324