Workflow to manage Minecraft Curseforge modpacks

cf_modpack_workflow.md

Required apps

1. Git or Github Desktop
2. ModpackUploader
3. Cat-Downloader-Legacy
4. Cat-Downloader-Legacy_Setup

Curseforge

1. Create custom instance in the Curseforge App
2. Add mods
3. Test compatibility of added mods

Add automation stuff

1. create automation folder in %HOMEPATH%/curseforge/minecraft/Instances/<modpackname>
2. Extract ModpackUploader in %HOMEPATH%/curseforge/minecraft/Instances/<modpackname>/automation
3. Fill in the settings.ps1 file with your modpack information and change $INSTANCE_ROOT value to ("$PSScriptRoot/.." | Resolve-Path)
4. Fill in the secrets.ps1 file with your CurseForge Upload API Token.
5. Run the modpack-uploader.ps1 when you're ready to upload your modpack to Curseforge
6. update Curseforge Instance through the launcher (minecraftinstance.json will be updated)

Git workflow (windows)

(create a blank repo in Github)

  cd %HOMEPATH%/curseforge/minecraft/Instances/<modpackname>
  git init .

edit .gitignore (e.g. https://github.com/adamico/mechanical-mastery-plus/blob/main/.gitignore)

  git add .
  git commit -m "initial commit"

Collab and beta testing without using CF

1. copy Cat-Downloader-Legacy and Cat-Downloader-Legacy_Setup.bat in %HOMEPATH%/curseforge/minecraft/Instances/<modpackname>/automation
2. rename Cat-Downloader-Legacy-.jar to Cat-Downloader-Legacy.jar
3. launch Cat-Downloader-Legacy_Setup.bat