ℹ️ Requires a Team plan
Anchorpoint allows to lock files for other team members to block conflicts (overwriting each other). File locking is possible in any project, both in a Git repository and on a Dropbox, Google Drive etc.
If a file is locked it is write protected for others if they also use Anchorpoint. A user thumbnail shows who locked the file.
Just select one or more files and choose Lock in the context menu. Immediately the locks are transferred to all participants that are currently using Anchorpoint.
In a Git project, binary files are automatically locked as soon as they are modified. So you don’t have to lock them manually. The locks are removed as soon as the files are pushed to the remote server. If you want to apply this to text files as well, you need to adjust the auto locking in “Project Settings”/”Git”
In this case .unity and .cs files would be also locked automatically.
If you have created the lock yourself, you can right-click and Unlock to unlock it for others.
You can also unlock the files of other users, for example if they have gone on vacation and forgot to unlock their files. In this case, after the unlock in Timeline entry is created to document who has unlocked the files. This way it is easier to find out who has to talk to whom in case of file conflicts.
If files are read-only, they cannot be easily overwritten by others. Some applications (Unreal Engine, Visual Studio Code) allow a force override, which can write files despite lock. But they show a corresponding warning.
File locking for Unity projects#
Unity does not respect the read-only property by default, but there is a fix available. Read more about Git with Unity
Write protection is not possible on a NAS (mounted drive) and on the cloud drive.