Why Git users switch
How Git users benefit from Unity’s version control
Unity Plastic SCM is built for game development. Here’s what you stand to gain when you upgrade from Git.
Better collaboration with artists
Artists can use Plastic SCM independently via Gluon, an easy-to-use workflow with file locking. Coders maintain their standard workflow with full branching and merging.
Work centralized or distributed
Choosing a VCS often means deciding whether to work centralized or distributed. Plastic has both: Get the speed and power of Git-style workflows with Perforce-like scalability.
Simplify maintenance with greater flexibility
Plastic SCM supports multiple workflows and large files out of the box, so you don’t need to maintain redundant systems or add-ons. Keep your toolchain lean and highly performant.
Unity’s DevOps solutions give programmers a wide range of functionality while keeping things streamlined for artists. See something missing from the list? Check out our DevOps roadmap.
Save time and minimize task-switching
Unity’s code-aware merge tech, SemanticMerge, tracks moved code to help you focus only on the relevant changes. By analyzing syntax, it automates 16–30% of code merges normally requiring a manual merge, drastically reducing merge conflicts that will distract from your workflow.
Plastic SCM will analyze a refactor and assess whether parts of the code, such as a method, have been moved, even across multiple files. This allows you to focus your review on only the most substantial changes. It supports C#, Java, VB.NET, and more.
Use as a Git client
Plastic SCM’s GitSync provides bidirectional synchronization between Plastic and Git. Plastic communicates with Git network protocols to push and pull packages and merges to a remote Git server (and the reverse). This allows you to use the Plastic GUI as a Git client: Because Plastic is structured somewhat similarly to Git, you can exchange all changesets, branches, and merges between them.
Fast import and export
Plastic implements fast-import and fast-export commands, all of which are totally compatible with their Git counterparts. These commands are used to import your project from Git to Plastic, and as a way to safely move away from Plastic if you ever need to. For regular daily operations, GitSync is an easier choice.
Utilize the Git ecosystem
Any tool in Git’s ecosystem can connect to Plastic instantly using their native Git functionalities. Teams using Plastic can then benefit from all the DevOps, CI, and project management integrations developed specifically for Git.
GitServer is GitSync’s server-side counterpart. It closes the Git interoperability loop by allowing Plastic SCM to serve repositories using Git protocols (Git and HTTP supported).