Skip to content

Instantly share code, notes, and snippets.

@adamico
Last active September 28, 2023 14:46
Show Gist options
  • Select an option

  • Save adamico/5c44ab8150b6716a51aa663cbb7c4ad3 to your computer and use it in GitHub Desktop.

Select an option

Save adamico/5c44ab8150b6716a51aa663cbb7c4ad3 to your computer and use it in GitHub Desktop.
Workflow to manage Minecraft Curseforge modpacks

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

Collab and testing without using CF alpha/beta releases

  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 WIP

Git workflow (windows)

WIP

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment