Modpacks and Profiles

Should I make a modpack or a profile?

Profiles are made up of a list of mods and configs for those mods. In most cases, profiles are faster and easier to make and use than modpacks. Use a profile if:

• You just want to share the same mods and settings with your friends.

Modpacks are packages uploaded to Thunderstore with the modpackcategory. They contain a list of mods as dependency strings in the manifest.json file and configs for those mods. Modpacks can also contain additional files (even entire mods). Use a modpack if:

• You plan on updating your mod list or settings regularly, such as for a dedicated server.

• You want your mod list and settings to be publicly available on the Thunderstore site.

How do I create a Profile?

Click the Share button or go to Settings -> Profile -> Export profile as code to generate and profile code and copy it to your clipboard.

Share this code using Steam, Discord, or any other text app. Importing a profile from this code will download the profile's mods and configs.

How do I import a Profile?

Profiles can be imported by code or file in the mod manager.

How do I create a Modpack?

Modpacks use the same format as any package on Thunderstore. See Creating a Package for instructions on how to properly format a package.

To add mods to your modpack, you need to add the dependency string for each mod to your manifest.json file. You can find the dependency string for a package on its page on the Thunderstore website or by using the "Show dependency strings" option in the mod manager Settings.

In most cases, you'll also want your configs for each mod as well. In the mod manager Settings, select "Browse profile folder" which should open a new window like the one below.

Open the BepInEx folder and find your config folder.

Copy just the config folder into your package. Do not copy the core or plugins folders, modpacks usually don't contain any actual code or assets themselves.

Zip up your files and upload the zip to Thunderstore.