There are just two questions I want ask:
BTW, my cocos creator version is 2.4.10 .
- If the project setting is included in the version control, but its settings include the preview setting and other settings related to personal development habits, so that after each update, the preview setting on your side will be overwritten. Is there a solution?
- Usually, when developing a game, one version control of one game is carried out in one cocos project, so that the project setting will not fight. But if the game is very light and needs to be mass-produced, is it possible that multiple games are in one cocos project? Do a version control? In this way, multiple games can be managed and developed in one cocos project, reducing development costs.
Sorry for the late reply.
- project settings can be placed on version control. But different people can ignore the settings on version control (update or commit) by adding .ignore configuration.
- it is possible for multiple people to work together on a project. There are usually several ways to do this.
- Putting different games into different bundles for loading. (But there is no way to nest bundles inside subgames)
- Set different games to different prefabs and load and unload prefabs when you need to switch games (this will limit the cases where all games fit into the same scenario)
- Switch different games as different scenarios and place them in different paths for loading. (This can be implemented by referring to the example project provided by the engine by default)
