Working with multiple people on 1 terrain
this is an exemple of methodologie of work to make big map and have multplie people working on it
this system is use for the zimnitrita map
However Seems that the SVN is a better solution regarding binarize file but its a bit old so we have prefer to host a custom githib
- Introduction and Software required
- Gitea configuration and user permission
- Cloning the repo in github desktop
- Add the project to Enfusion Workbench
- Import info and rules to work with sync (avoid push problem)
- Send the work
- Terrain modification (avoid loosing modification)
Introduction and Software required
- Install and configure a private git (we are using gitea because of the easy install step) (admin part)
install gitea with portainer: https://docs.gitea.com/next/installation/install-with-docker
- people need to create an account on the git you created
2. we are using the github desktop software to avoid people working with command line and because it’s easy to use also https://desktop.github.com/
Unfortunately you will need also to create an account on github in order to use their software
https://github.com/signup?source=login
Gitea configuration and user permission
Add people to the repository of the map (admin part) (add people in the Mapper teams in order for them to have access to the map)
After being add people will get access to the repository
so they can clone the url of the online repository
Cloning the repo in github desktop
Add this url inside the github desktop software
you will have to add the credential you have create for your private git (step 2 of this tutorial)
Wait for the cloning to be over
Add the project to Enfusion Workbench
Inside the workbench you will have to add the repository you've just download
Make a rule and explain to everybody that they have to work inside their tilt and also have a personal layer
Import info and rules to work with sync (avoid push problem)
Once they have finish their work and wanted to push their work they absolutely need to fetch and pull the update from the repository in you private git to avoid any conflict
This represent 95% problem with sync so please be carful
Send the work
Prepare the sending of your work
you will need to give a name to your commit
send your commit to the repository in order for the other mapper to have the update
Terrain modification (avoid loosing modification)
Exception case on modifying terrain
terrain wont work like the props layer because it is considering as one layer and everyone will erase the work of the other if they don't work in tiles
In order to work with tile i suggest you to make a screenshot and try to make some rule on who works on which tile
To see the tile in the engine go to the the terrain tool and place the cursor in center of your screen
You can also use the debug mode to see each limit of tile (kinda like the F3 in minecraft to see chunk border)
- to open the debug menu make windows key + alt / or windows key + left control
go to render menu with the up and down arrow key and enter with the right arrow key
to display will need to follow this patch: render -> terrain menu -> tiles bonding screen
