Skip to main content

VRChat Version Control Guide

Version control is the protection layer that sits next to ALCOM.

Use ALCOM to manage packages and project setup. Use version control to protect work, coordinate with collaborators, and recover when someone breaks something important.

If you are working alone, version control is still worth it. If you are working with other people, it stops being optional very quickly.

What This Guide Covers​

This guide is split into several focused sections:

How This Fits With ALCOM​

The clean mental model is:

  • ALCOM manages project setup, repositories, and VRChat packages
  • Version control manages history, collaboration, rollback, and recovery

Do not expect ALCOM to replace source control. Do not expect source control to solve package-management decisions for you.

Use both, and use them for different jobs.

Which Tool Should You Use?​

Use PlasticSCM if:

  • You're working with large Unity projects
  • You have lots of textures, FBX files, and 3D assets
  • You want better handling of Unity's binary files
  • You want a workflow that maps well to scene-heavy collaboration

Use GitHub if:

  • You're comfortable with Git
  • You want free unlimited private repositories
  • You're okay with some extra setup for large files

Choose the tool that fits your team and follow the corresponding guide. Regardless of which tool you choose, read the best-practices page first. That is where most of the real pain is avoided.