Hi everyone!
We are already looking into ways to improve communication internally! This has been something on our mind, and something that’s been communicated to us for a good while.
What are key features the creator1 community would like to see from VRChat’s communication pipeline?
Here’s some things we already have in mind. Check these out, let us know what you think about them, and tell us your own ideas.
We’ll be reviewing feedback through early January and talk about next steps in a February Developer Update.
Dedicated Discord Server for Creators
Right now, creators have to vie for attention on our massive public Discord. This… is not ideal!
We think a dedicated Discord would help a lot here.
This server would serve as a place for discussion and feedback, and also provide a place where we could use automation like TicketBot to provide more direct, dedicated support and feedback when required.
This server would also give us the opportunity to hold Creator-centric Stages and events to help communication. It would also allow us to hold more targeted testing and feedback sessions on upcoming changes and features. It could also provide a place for creators to support each other and chat directly with VRChat developers.
We have a handful of questions still pending with this idea, though:
- How and when does a Creator get an invite to the server?
- Are there requirements? What are they?
… among dozens of others! We think we have some of the answers, but we want to hear what you think.
Creator Partnership Program
A Creator Partnership Program is almost certainly in the future cards for VRChat, although the structure and layout of such a program is still in the planning stages. How would you expect this program to work? What services would you expect it to have? What requirements? We want to hear what you have to say!
Structured Release Pipelines and/or Cadences
With our most recent SDK and VCC update, a lot of people were blindsided by the lack of information. “btw, Unity 2022 is out, have fun” isn’t very helpful!
We think that establishing a structured release pipeline or cadence and then publishing that information would help mitigate this problem a lot, so that those releases aren’t as vulnerable to unexpected issues pushing things faster. This would also mean we’d be communicating delays.
Improved Messaging Channels
By “channels”, I mean “ways we can reach you.” A lot of the problem with contacting creators is that you’re so dang hard to find! You have to actively come looking for us. Sometimes, though, we need to tell you something.
As such, we’re looking into getting resources to implement creator notifications or messaging into the VCC, kind of like a Creators-centric news feed.
Improved In-App Articles
The in-app articles we have are pretty good, but for technical reasons, are very hard to write! (the format is really bad omg) We want to use them more, but this difficulty in writing them makes it hard to use them as a tool.
We have plans to improve these in-app articles in the coming year, and part of those improvements could also include a way for us to target users who have worlds or avatars uploaded to their account. This would let us let people know if an impending change or update might affect them.
Note 1
1By “creator” in this post’s particular usage, we mean any type of creator related to VRChat creation where you use the SDK. This is including but not limited to:
- World creators
- Avatar creators
- Udon programmers
- Tool creators
- Shader creators
- Asset/prefab creators
In some of the solutions and methods we list above, other creators might also benefit – for example, we envision the Creators Discord being a place where video content creators could also go to provide feedback and ask questions.