So, this involves the whole process of making missions, placing objects and creating triggers and scripts and whatever else is needed.įrom what I understand from your answers, we should use different software for object placement, the MCC sandbox, and different for scripting, say google docs.Ībout Github. I myself know programming, not Arma scripting, and would like to help them with scripting. Two of them have advanced knowledge in mission making, but not scripting, and the third is beginning now. We have three mission makers in our unit that want to collaborate and create missions together. It also offers you a nice web based user interface so you don't have to use the CLI commands I described for all steps. Just a mini walkthrough on git, github uses git but basically offers to host the things for you. If there are merge conflicts, resolve them with a text editor and commit changes as usual. If the work is finished, the changes get merged with the master branch ( git checkout master, git merge ). Then he will create a new branch ( git checkout -b ) and make all changes on that branch. * ).Ĭollaboration normally happens on separate branches, when someone works on something, he synchronizes with the latest files on the server ( git pull remote master) before starting. Add all files you want to have version controlled ( git add ), commit the added files ( git commit -m "Initial Commit") and copy the repository to a publicly available server ( scp. Get Git for Windows, it comes with Git Bash, and type git init in the mission folder.
Or just git, in case you don't want the repository to be public.
0 kommentar(er)
