Hi,
Just a quick note on sourcetree and PlayMaker content.
The restrictions are the same for PlayMaker than any other binary file when sharing over a github rep or similar, MEcanim files, audio files, animation files, scenes, prefabs, they all suffer this, and so there is no reason why you should not anyway use sourcetree:
-- organize your team work around this limitation. USe simple technics like a quick morning chat on who will do what, "you'll work on this prefab, this fsm, and I'll work on this and that", essentially, you will need to "lock" editing as an aggrement on all developers, and that works very well.
-- organize your content to match this limitation
-- use fsm templates, then you can edit a gameobject and/or a template independantly
-- cut down your features in very distinct blocks, scenes, prefabs, folders, etc
-- do pair programming and work together, it's incredible how effective that is, it may seems like a waiste, but I have a pretty good experience going for over a year now and I am the first one surprised. we are sharing a huge project on sourcetree, and conflicts are very rare and often more because we worked on the same scene or prefab than on the same PlayMaker Fsm, again because we are both aware of what the other do. and so when we detect we need to edit something the other has a lock on, we just call and sort it out one way or the other.
Bye,
Jean