The Modrinth modpack format (.mrpack) is a simple format that lets you store modpacks. This is the only format of modpack that can be uploaded to Modrinth.
Fields
formatVersion
The version of the format, stored as a number. The current value at the time of writing is 1.
game
The game of the modpack, stored as a string. The only available type is minecraft.
versionId
A unique identifier for this specific version of the modpack.
name
Human-readable name of the modpack.
summary (optional)
A short description of this modpack.
files
The files array contains a list of files for the modpack that needs to be downloaded. Each item in this array contains the following:
path
The destination path of this file, relative to the Minecraft instance directory. For example, mods/MyMod.jar resolves to .minecraft/mods/MyMod.jar.
Danger: If you implement an "import ZIP" feature or similar, make sure this field doesn't exit the Minecraft instance directory for security reasons. To do this, make sure it doesn't contain .. or start with a drive name (i.e., [A-Z]:/, [A-Z]:\, /, and \).
Any files uploaded to Modrinth are validated automatically to ensure they do not contain this.
hashes
The hashes of the file specified. This MUST contain the SHA1 hash and the SHA512 hash. Other hashes are optional, but will usually be ignored. This is formatted as such:
"hashes": {
"sha1": "cc297357ff0031f805a744ca3a1378a112c2ddf4",
"sha512": "d0760a2df6f123fb3546080a85f3a44608e1f8ad9f9f7c57b5380cf72235ad380a5bbd494263639032d63bb0f0c9e0847a62426a6028a73a4b4c8e7734b4e8f5"
}env (optional)
For files that only exist on a specific environment, this field allows that to be specified. It's an object which contains a client and server value. This uses the Modrinth client/server type specifications. For example:
"env": {
"client": "required",
"server": "unsupported"
}In the above example, this is a client-only file. It cannot be installed server side. Both side types can only be the following values: required, optional, unsupported.
Tip: For optional mods, we recommend showing a dialog to the user that allows them to select which optional files they would like to install.
server refers to the dedicated server. Even though clients technically have a logical server, if something is marked server only, it should not be installed on the client.
downloads
An array containing HTTPS URLs where this file may be downloaded. URIs MUST NOT contain unencoded spaces or any other illegal characters according to RFC 3986.
When uploading to Modrinth, the pack is validated so that only URIs from the following domains are allowed:
cdn.modrinth.comgithub.comraw.githubusercontent.comgitlab.com
Other platforms implementing the specification SHOULD have a defined set of whitelisted domains.
HTTP 3xx redirects MUST be followed for a reasonable number of redirections (we recommend three minimum).
fileSize
An integer containing the size of the file, in bytes. This is mostly provided as a utility for launchers to allow use of progress bars.
dependencies
This object contains a list of IDs and version numbers that launchers will use in order to know what to install.
Available dependency IDs are:
minecraft- The Minecraft gameforge- The Minecraft Forge mod loaderneoforge- The NeoForge mod loaderfabric-loader- The Fabric loaderquilt-loader- The Quilt loader
Warning: We may add other supported dependency IDs at any time. Please ensure your application handles this.
An example dependencies object:
"dependencies": {
"minecraft": "1.18.2",
"forge": "40.1.0"
}Storage
When stored on disk, the modpack MUST be in ZIP format (MIME type application/x-modrinth-modpack+zip), using the .mrpack extension. The main metadata of the modpack MUST be stored with UTF-8 encoding at modrinth.index.json in the root of the zip.
Overrides
The zip may also contain a directory named overrides. Files in this directory will be copied to the root of the Minecraft Instance directory upon installation by the launcher. For example:
my_modpack.mrpack/
modrinth.index.json
overrides/
config/
mymod.cfg
options.txt
When installed, the contents of overrides will be copied to the Minecraft Instance directory and end up similar to this:
.minecraft/
config/
mymod.cfg
options.txt
Along with the traditional overrides folder, Modrinth also has a server overrides folder to eliminate the need for server packs.
Server overrides work in a layer based approach. This means server overrides folder (with the directory name server-overrides) will be applied after the overrides folder, overwriting its contents.
Here's an example:
my_modpack.mrpack/
modrinth.index.json
overrides/
config/
mymod.cfg
options.txt
server-overrides/
config/
mymod.cfg
servermod.cfg
When installed, the contents of overrides will be copied to the Minecraft Instance directory. Then the contents of the server-overrides will be copied and end up similar to this:
.minecraft/
config/
mymod.cfg
servermod.cfg
options.txt
Client Overrides
Modrinth also has a client overrides folder! The folders name is client-overrides. It is functionally equivalent to the server overrides folder (besides only being applied on the client), and works the same with the layer based approach.
Both the server and client override folders are optional.