Skip to main content

Maintenance and Recovery

ALCOM makes package management better. It does not remove the need for discipline.

For VRChat projects, stability comes from three things working together:

  • ALCOM for package management
  • version control for tracked changes
  • backups before risky edits

The Rule​

Before any risky change:

  • make a commit
  • or make a backup
  • preferably both

Risky changes include:

  • SDK upgrades
  • shader-framework upgrades
  • large package installs
  • Unity version changes
  • repository source changes

Healthy Project Maintenance​

To keep projects stable:

  • keep templates lean enough that you still trust the starting state they produce
  • update packages in small groups
  • keep repositories tidy
  • avoid stale experimental packages sitting in production projects
  • test after upgrades, not days later
  • keep one clean rollback point before every major package change

Recovery Mindset​

If a project breaks after package changes, do not keep stacking fixes on top of the broken state.

Instead:

  1. identify the last known good state
  2. restore from version control or backup
  3. repeat the change more carefully
  4. isolate which package or upgrade caused the issue

That is usually faster than trying to improvisationally patch a broken project back together.

Good Recovery Tools​

Use at least one of these:

  • Git or Plastic for tracked project history
  • zipped project snapshots before major changes
  • separate test projects for package experiments

ALCOM improves the package workflow, but your real safety net is still external project history.

If You Change Machines​

ALCOM is especially nice when your workflow spans multiple operating systems, but the same rules still apply:

  • keep project paths organized
  • keep repositories documented
  • keep version control current
  • verify Unity installs before opening important projects

If the project exists in version control, getting onto a new machine becomes much less painful.

Common Recovery Scenarios​

Package update broke the project​

  • restore to the last good state
  • re-read the changelog
  • retry the update in smaller steps

Project opens but upload behavior is wrong​

  • confirm the correct packages are installed
  • check whether a dependency changed during update
  • compare against the last working commit

Repository confusion​

  • verify which repositories are configured
  • remove old or duplicate sources you do not need
  • avoid mixing too many package sources without a reason

You are not sure what changed​

  • stop editing
  • compare against version control
  • check recent package changes first

Recommendation​

Use ALCOM as the day-to-day project and package manager.

Use version control and backups as the actual recovery system.

And if you create the same kinds of projects repeatedly, use Templates and Project Starters so your recovery story starts from a cleaner baseline in the first place.