Would you open the source code of VCC?

[Sayamame-beans]

VCC has a lot of issues. Some of them are critical (though you may not recognize them as such). For example,

• Unable to change project creation location in certain cases. (#249)
• New registrations with the same id as the already registered repositories are possible, which breaks the VCC behavior. (#259)
• legacyFiles and legacyFolders do not work in relatively common cases. (#298)
• When users with 1.x VCC (still exists!) update to 2.x, setting files get broken and VCC do not work properly. (#265, #266)
• Modifying settings.json from VPMCLI or any other tool while opening VCC(GUI) causes it to rollback when VCC closes. (#111)

Not only that, VCC also lacks important functions as a Package Manager. For example,

• Ability to specify multiple available Unity versions for each package. (#311) (Some tools support multiple Unity versions, others do not. If Unity2022 support comes, the current VPM will not handle them correctly.)
• Ability to inform about deprecated versions. (so called yank. #204)
• Solutions to the very frustrating problem that we have to wait for imports to complete one by one to install/update multiple packages. (#187, #331, #172)

Some developers are very motivated to solve such issues and/or identify the cause, but unfortunately, VCC does not publish the source code. Some issues have already been waiting for half a year for a response. If you do not have enough resources to solve such issues, please make VCC Source Available or Open Source so that the community gets a chance to solve them.

[momo-the-monster]

@Sayamame-beans - I have made this request earlier this year, waiting to hear back.

[Happyrobot33]

just giving a thumbs up to this, id love to contribute additions

[Sayamame-beans]

It seems really foolish to put off or completely forget about suggestions that users considered important or possibly needed in the future, thinking "hmmm, this doesn't seem important right now", only to have situations arise later where they are really needed. VRChat seems to have little foresight into what will happen in the future. This is true for the issues mentioned here, and also for those not mentioned ( #346 ).

When VCC first came out, I thought "This is a really cool system!" that could keep up with SDK updates and properly manage other tools. It was actually revolutionary. However, the current situation has had the exact opposite effect. At times, it broke projects, even though just updating VCC and doing a few standard steps. This is a reasonable situation that users should avoid updating.

It's not a good situation. It could have been possible to avoid this if OpenBeta ( #397 ) or the source had been available before release, but it wasn't, so I had to say "The latest VCC is unstable, so do not update it, wait for more information!" when the VCC version was unstable, and "Update your VCC to the latest x.x.x! Otherwise, your projects will be broken by a package that requires the latest!" when the VCC version was stable but made breaking changes.

Of course, I fully understand that there are some staff members who are very cooperative. However, that does not seem to be the company's policy. This is a tough situation to say the least, and we even think that it would be faster to give up on the official one and make an alternative to VCC in the Third-party. This is really sad.

This message may not change anything. But the recent series of problems have given the developer community a lot of doubts. I feel that a less than desirable situation is coming for everyone. Perhaps this is one of the parts that needs to change.