Setting Up a Modpack

Creating a New Modpack

To create a new modpack, run the pakku init command:

This will ask you to enter:

1. The name of the modpack.

2. The Minecraft versions supported by the modpack.

3. The mod loaders and their versions supported by the modpack.

4. The targeted platform of the modpack.

I will also set the version of the modpack to 0.0.1 and add config folder to the overrides.

If you made a mistake, you can change the properties of the modpack using the pakku set command.

Importing an Existing Modpack

To import an existing modpack, run the pakku import command with the <path> argument:

The <path> argument will only accept:

• CurseForge's modpack with the .zip extension or the CurseForge's manifest.json file.

• Modrinth's modpack with the .mrpack extension or the Modrinth's modrinth.index.json file.

Pakku automatically sets the targeted platform of your modpack based on the file you import.

Migrating Modpack's Platform or Importing as Multiplatform Modpack

You can import a CurseForge modpack as a Modrinth modpack or vice versa by doing the following:

You can import an existing CurseForge or Modrinth modpack as a multiplatform modpack by doing the following:

Configuring CurseForge Access

Pakku requires users to provide their own CurseForge API key when accessing CurseForge.

According to CurseForge for Studios REST API documentation, the API key can be generated in the CurseForge for Studios developer console.

Follow these steps to configure the access:

1. Login to the developer console.

2. Go to the "API keys" tab:

   

3. Copy your API key.

4. Enter your API key to the prompt provided by Pakku, or use the pakku credentials set command:

   pakku credentials set --cf-api-key *********************

   java -jar pakku.jar credentials set --cf-api-key *********************