# Repo overhaul

As you might've heard, the plan is to overhaul the repo just after the release of Tanks.

The way Swifty works is that it'll download all mods (folder) for a repo to your selected download location. When you start the game, only matching mods for the repo you've selected will launch with the game. This allows us to share mods between different repos without having to download them for each separate repo. This is also the reason why Swifty doesn't delete folders.

The reason we're doing this is to not load a fuckton of mods which makes the game unstable and forcing everyone to download all mods. The current plan is to have 3 repos. Core, main and blended (names not certain).

### Core repo
 Contains mods which all repos use. This would have @cba, @ace, @acex, @acre, and some @fp mod. Perhaps @NIarsenal.

 While core can be mounted on the server it will likely not often be mounted due to having barely any content. It provides a starting ground for missions that have "no dependencies" between the other repos.

### Main repo
This is the main repository, *it will always be used on standard time Sunday ops*. This is for people who will only play on Sundays and those with limited bandwith who do not want to keep up with the content in the blended repo. As of the time I'm writing this it will most likely contain CUP and some mods that we currently have once they have been "checked" for errors and rpt spam.

### Blended repo
This is a more "moving" repo where mods can be added and removed more often. As an example it might contain RHS for 2-3 months and after that WW2 mods. To be used during midweek and saturday ops as it might be more prone to unstable gameplay. Any major change means all missions *will be wiped*.


### Deployment, questions and remaining issues

* Moderators can deploy a repo to the server when needed. Technically there's a folder with keys, swifty-built repo and missions for each repo. When deploying e.g main, it'll take keys and missions from core and mods, keys and mission from main. The server's mpmissions, keys and repo folder is wiped every deploy, and symlinked from the repos. The startup scripts for server and hc is generated each deploy.

* Old missions WILL BE WIPED but zipped up before this overhaul. There's no guarantee they will work as we don't know what content the main repo will have. The idea is that main will have fully-working mods with barely any errors.

* As swifty doesn't delete folders, the blended repo requires user action to remove old mods when there's a major change. A way around this is to fill up the repo with pre-named mods, for example @mod1, @mod2, @mod3. It won't say what the content it has, but doesn't require users to constantly wipe the folders that blended had. Afaik this shouldn't be issue and the name of the mod folder doesn't matter.

* The bot needs an update to take into account which repo to upload for. Most likely it'll upload to the servers mpmissions and the provided repo's mpmissions. This mean a mission for blended could be uploaded to the server while it is currently running main; afaik it shouldn't be an issue unless someone selects the mission and it does an #include or similar from a mod not mounted.