Skip to content

Creating a modpack

1. Initializing:

Create an empty modpack file: modman init [file_name] (file_name without .yml)

2. Customizing:

Edit the file you've just created, it could look like this:

  name: BeautyCraft
  description: A simple client side modpack for making Minecraft more beautiful, more immersive and more playable.
  project_version: 3.0.1

  minecraft_version: 1.21.5
  loader: fabric
  type: client

  projects:
    - sound-physics-remastered
    - shulkerboxtooltip
    - spawned-eggs
    - iris
    - appleskin

  overrides: overrides-beauty-craft

The option type can be set to server, client or both:

  • server: Include all projects, don't include information about type
  • client: Same as server but without server-side-only projects
  • both: Inclue all projects, include information about type, makes Modpack usable on client and server

3. Creating:

Now create the .mrpack file with modman create [file] (file is the one from the first step).

You can use the options -n, --name [name], -d, --description [description], -v, --v [project_version], -t, --type [type] and -o, --o [overrides] to override values in the modman file temporarily (useful when creating a client-side version of a server-side modpack).

Notes:

  • overrides is a folder which either can be used with an absolute path (/home/user/overrides) or a relative path (./overrides). When using a relative path, the folder must be in the same directory in which you are running the command. What overrides can contain is explained here.