Home

PackUpdate is a small tool to update Server-Specific Modpacks inside of MultiMC.

Getting started

Setting up a server requires you to host a small csv file at any URL. Furthermore you should either host the mods yourself or collect a list of URLs.

(Alternative 1) Building the CSV file for your pack

Create a zip file for all of your config files. The config files should reside at the root of the zip file.
Optionally create a second file for all non-config resources.

Next, create the CSV file

The CSV file should contain the following fields:

• The name of the Component (should be stable across versions)
• The version of the Component
• The download URL. This should be a direct link, however PackUpdate does follow redirect. CurseForge direct download links work as well.
• the component type. Currently supported are: mod, resources, config and forge. For more information see Component Types
• (Optional, but highly recommended) A SHA-256 hash sum of the respective file
• (Optional) a semicolon separated list of flags. For more information see Flags

(Alternative 2) Automate building the CSV file for your pack

TBD.

Creating the Minecraft instance

Create a new instance in MultiMC and drop the UpdaterUpdater.jar in its directory. Adjust settings as you want (and install forge!). Then set the Pre-Launch hook to "$INST_DIR/UpdaterUpdater.jar" <url of your csv>. Now you should launch your game and test if it works. If you want you can opt into beta releases by changing the beta value in $INST_MC_DIR/packupdate/updater.properties to true. Alternatively you can use the PackUpdate jar directly, however this makes updating PackUpdate itself much harder.

Exporting the MultiMC instance

Use MultiMCs feature to export the instance. Make sure to include the following:

• instance.cfg
• mmc-pack.json
• UpdaterUpdater.jar
• packupdate/updater.properties if you have changed anything