Unity Version Control with Unity 6

Navigate Unity accounts and Unity Cloud with confidence as you master account setup, verification, and the terminology of seeds and organizations in Unity version control.

Explore how users, organizations, and seats govern access to Unity's services and version control via Unity Cloud, enabling collaboration through paid and free tiers.

Discover how the Plastic SCM plugin integrates with Unity to manage version control, view pending changes, changesets, and check in, and use the Plastic app for merging and branches.

Learn to use the plastic app as a standalone, Unity-agnostic version control tool, exploring the cloud dashboard, repositories, workspaces, branch explorer, and pending changes.

Explore changesets in Unity version control with plastic, learning how they snapshot project states, how to switch workspaces, and how identifiers and private files affect version history.

Explore how plastic handles file statuses in Unity version control: private to added and edit, how to check in files, manage change sets, and undo unintended additions.

Explore how Unity auto-generated private files in the assets folder, how Plastic treats generated versus added files, and how undo and checkout affect file states in version control.

Learn how to ignore unwanted Unity files in Plastic version control using ignore dot conf, focusing on library, manifest, packages, and assets, with simple rules and advanced wildcards.

Explore how version control tracks project snapshots with diffing in Unity, comparing changesets to reveal edits across scene, asset, and script files stored as text.

Diff and review changes across input actions, scene edits, and the player’s start position, using Plastic diff tools with per-file blocks and semantic, visual, and image diff for binary files.

Discover how to use branches in plastic version control to organize changesets, create and switch branches like cubes and spheres, and manage origins and deletions.

Learn how to integrate changes from feature branches into the main branch in Unity version control, using source, destination, and changesets to review and complete merges.

Explore merge conflicts in Unity and learn how version control handles divergent changes through conflict resolution, manual merging, and practical examples of asset and script changes.

Explore how evil twin conflict arises in Unity version control when two branches create identical folders, and learn three resolution options and best practices to avoid asset folder issues.

Discover how Unity scenes function as central hubs for prototyping and how plastic manages merges, including automatic vs manual conflict resolution in three-way merges with base, source, and destination.

Learn how prefabs reduce merge conflicts in Unity version control by isolating changes to prefab data, enabling clean merges across level designer branches and team A and team B.

Resolve script conflicts by illustrating how two developers' changes on the same game manager script trigger a three-way merge and require manual or automatic resolution using the plastic merge tool.

Explore version control in Unity by reverse-engineering a finished Rollerball project, using Unity Learn assets and the package manager to simulate a real-world workflow.

Plan a Unity project with version control by dividing it into packages and applying task-based branches, outlining five steps: level, movement, core logic, aesthetics, and UI.

Create a new Unity project with Unity Hub and Unity version 22.3.29. Connect the project to Unity Cloud and version control, and configure the repository name if desired.

Learn to use the ignore file to keep private and copied project files out of version control in the Unity editor, focusing on actual changes and the intended workflow.

Ignore the current directory by updating the ignore file, then verify the test file is excluded from version control and shows as a grey minus in pending changes.

Branch from the latest changeset to create the level, add a ground plane, walls, and a player sphere, then adjust the camera and lighting, and merge back to main.

Implement a basic player controller by capturing vertical and horizontal input, applying movement to the rigid body, and add a camera follow script to track the player.

Refactor the rollerball project to reduce instability through version-control practices, using branches, change sets, and merges to separate refactoring from feature work while reorganizing assets and scripts.

Add game logic by implementing collision detection for pickups with OnTriggerEnter, using the pickup tag to deactivate collected items, and manage changes with shelving and branching in plastic.

Use prefabs to optimize version control by converting pickups into a prefab, keeping scene files lighter and changes tracked on the prefab asset rather than the scene.

Create a new branch and enhance the pickups by applying a new material and adding a rotation script to the prefab, keeping the scene file unchanged for easy Plastic merges.

Create and connect UI in Unity with a canvas and text elements, updating the score and win message in the player controller. Use a hotfix workflow to fix live issues.

Learn to collaborate on a Unity project using Plastic as version control, inviting members, managing seats in Unity Cloud, and accessing projects via changesets across devices.

Cindy makes her first contribution by adding a blue material to the cube, triggering changes, resolving conflicts, and updating workspaces via incoming changes to sync with Andy.

Learn how the permissions hierarchy simplifies collaboration by configuring top-level permissions that auto-inherit to cloud server, repositories, branches, and paths, with optional deny overrides and per-object controls.

Set and reflect user permissions between Unity Cloud and Plastic by navigating the DevOps and repository settings, understanding organization versus repository permissions, inheritance, and overrides.

Resolve the Unity version control 'not connected' issue by ensuring you have the correct permissions or login to a user with access.