What is this?
Unity Version Control (formerly Plastic SCM) is a version control system built for game development studios of all sizes, supporting any engine including Unity and Unreal. It offers optimized workflows for both programmers and artists, with deep integration into the Unity Editor through a dedicated package.
What did you do?
I worked as a C# software engineer on the Unity Editor integration package for nearly 2 years. Some highlights of what I built and maintained:
- Implemented a status bar from scratch, showing the current branch, incoming updates, and package news directly in the Editor. I collaborated closely with the UI/UX designer throughout the process.
- Added status icons to the changed files list and the Unity project view, allowing users to visually differentiate between created, updated, and deleted items.
- Bridged features between the Unity Version Control desktop app and the Editor package, such as launching the merge tool from within the Editor when a merge conflict is detected.
- Fixed a significant performance issue caused by uncached icon retrieval — icons were being fetched from disk every frame, and I reworked the system to cache them, resolving user-reported performance problems.
- Added a date sort menu to the changed files list.
- Maintained the package release pipeline, including packaging, changelogs, and publishing to the Unity Editor package system.
How was this built?
- Unity (of course!) and C# for developing the package.
- Unity IMGUI + Unity UI Toolkit for UI implementation.
- Figma for collaborating with the UI/UX designer.