In a distributed version control system that uses email, it is possible that two scripts miss each other on the way between two developers. Code Co-op deals with such situations by making one script win and the other becomes a side branch. When you receive a script that loses, you'll see it in your history marked as Branch—it will be greyed out and italic. The script contents are still accessible and can be brought into the project trunk through a merge. This is typically done by the person whos script was branched, but i doesn't have to be. Any one can merge a branch into the trunk.
When you try to execute an incoming script—whether manually or in auto-sync mode—and it conflicts with a check-in you did, Code Co-op will display a warning dialog. The dialog will tell you that there is a conflict and that your check-in script has become a branch..
At any time you can go to the History tab and see your check-in script marked as a Branch. In order to bring your branched script/s into the main project trunk, you need to merge the local branch.
In order to avoid conflicts, it's a good idea to always check your e-mail for incoming scripts before doing a check-in. Conflicts may also occasionally happen in a LAN-based setup, especially when some computers are off-line.