Level Designer Workflow
Unity Version Control Workflow for Level Designers
A level designer using Unity Version Control should update before editing, acquire locks only for high-risk shared assets, keep scene and prefab changes focused, review the pending changes as Unity structure, check in a clear changeset, and validate the complete level before merge.
Before editing a level
- Update the workspace to the latest approved changeset or branch state.
- Open the level through the team's documented bootstrap or additive scene flow.
- Check scene, prefab, lighting, navigation, and binary asset ownership.
- Acquire a Smart Lock for assets covered by lock rules or announce temporary ownership.
- Confirm that no pending merge or unresolved file conflict exists.
Do not begin a large layout edit from an outdated workspace. UVCS Smart Locks can also reject an outdated lock request when a newer retained revision exists.
Keep the edit scope reviewable
- Work in the smallest owned additive scene or prefab.
- Avoid unrelated hierarchy cleanup, mass renaming, or reserialization.
- Use prefabs for reusable encounter and prop groups.
- Keep scene-specific placement in the scene and shared structure in the prefab source.
- Separate lighting, navigation, or generated-data operations when they create broad churn.
- Save intentionally and inspect the Pending Changes list before continuing.
Review changes without reading raw YAML
MergeSight UVCS workflow for level designers can compare the current workspace or concrete changesets and show scene or prefab changes as GameObjects, components, properties, hierarchy moves, reorders, references, and overrides.
Before check-in, answer:
- Which level objects were added, removed, moved, or reordered?
- Did any object move to a different parent or additive scene?
- Which transforms, triggers, cameras, colliders, or serialized values changed?
- Are prefab overrides intentional and minimal?
- Do object, prefab, material, and data references point to the expected targets?
- Did Unity save unrelated content?
Create a useful UVCS changeset
- Revert unintended pending files.
- Include matching meta files for added, moved, or renamed assets.
- Write a changeset comment that names the level area and visible behavior.
- Check in one coherent change rather than mixing several unrelated tasks.
- Request review from the level owner and technical reviewer when scripts or references changed.
- Release or transition locks according to the branch and destination policy.
If UVCS reports a scene or prefab conflict
Keep the merge state and preserve base, destination, and source. Do not mark the file resolved by choosing the complete source or destination before inventorying both change sets. Review hierarchy, references, overrides, and delete-versus-edit decisions, preview the result, then validate in Unity.
Level validation checklist
| Area | Designer check |
|---|---|
| Composition | All additive scenes load and objects belong to the intended scene. |
| Hierarchy | Parents, sibling order, active state, layers, and tags are correct. |
| Gameplay | Triggers, spawn points, checkpoints, objectives, and encounter data work. |
| Prefabs | Instances remain connected and overrides are intentional. |
| References | No missing scripts, materials, prefabs, or serialized object links appear. |
| Generated data | Lighting, navigation, occlusion, or other required data is current. |
Team policy that helps designers
- Visible ownership for shared scenes and generated data.
- Simple lock discovery and a documented stale-lock contact.
- Small branches and frequent changesets.
- Semantic review available inside Unity.
- Clear validation steps that do not require manually reading YAML.
- CI reports written in asset and object terms.
FAQ
Can level designers use Unity Version Control without Git?
Yes. UVCS provides desktop and Unity-integrated workflows around workspaces, changesets, branches, code reviews, merges, and Smart Locks.
Should level designers lock Unity scenes in UVCS?
Lock high-risk shared scenes or non-mergeable work when overlap cost is high. Prefer additive scenes and prefabs for normal parallel work rather than locking every level file.
Can level designers review scene changes without YAML?
Yes. A semantic Unity asset review can show GameObjects, hierarchy, components, properties, references, and prefab overrides instead of raw YAML lines.
What should a level-design changeset comment include?
Name the level area, intended visible or gameplay change, important scene or prefab files, generated data, and any validation or known follow-up.
Summary
Update and coordinate
Start from current workspace state and acquire only the locks the task actually needs.
Review level meaning
Inspect objects, hierarchy, transforms, references, overrides, and unintended saves.
Check in a coherent change
Use a clear changeset comment, required reviewers, and complete level validation.
A designer-friendly VCS workflow keeps source-control mechanics visible but expresses review and validation in level-design terms.
Next step
Set up the provider and changeset review flow with MergeSight for Unity Version Control.