Resource packs

MCME's resource packs give each region of Middle-earth its own look: Human, Mordor, Dwarven, Rohan and so on. Each pack lives in its own public GitHub repository under the MCME organisation. A shared tool repository, ResourcePackScripts, turns a pack into the zips players download, adds the shaders every pack shares, and runs the releases. These pages are for people who make or change a pack, and for staff who release one.

How the packs are organised

One repository per pack, named RP-<Name>: for example MCME/RP-Human. Each has two long-lived branches: development (work that is being tested) and master (what production builds).

Two kinds of pack:

	Sodium pack	Vanilla-only pack
Has 3D `.obj` models	Yes, in `assets/mcme/`	No
Zips per release	Six: Sodium, Vanilla and Lite, each also with Footprints	Two: the pack, and its Footprints copy
Converted by generateVanilla	Yes, twice (Vanilla and Lite)	No: the repository is zipped as it is
Examples	Human, Mordor, Paths of the Dead	Dwarven, Rohan, Lothlorien

The variants players can get:

Variant	What it is	Who gets it
Sodium	The pack as its makers write it. Its 3D models are `.obj` files that only render with the Special Model Loader client mod.	Players who join with the MCME modpack
Vanilla	Made from the Sodium variant by generateVanilla: every `.obj` model is baked into an ordinary block model, and shaders in the pack draw the real shape. Works without mods.	Every other client
Lite	A Vanilla variant with at most two models per block state, and simpler fluids. Smaller and lighter.	Players who choose it with `/rp client lite`
Footprints	A copy of a variant with the activator rail textures swapped for footprints.	Players who choose it with `/rp variant footprints`

The MCME modpack is installed with the MCME Installer. For 26.2 and 26.3 it includes Fabric, Sodium 0.9.2 and MCME's build of Special Model Loader, so it can show the Sodium variant.

ResourcePackScripts holds three things pack authors meet:

generateVanilla, the converter that makes the Vanilla and Lite variants from a Sodium pack. See How the conversion works.
The shader base, the shaders every pack shares (the baked models, water, fog, the action bar), which a script copies into each pack repository. See The shader base.
The release automation, which builds the zips and publishes them when staff type /rp release in game. See The release pipeline.

From repository to players

flowchart LR
    push["Push to development"] --> rel1["/rp release on the RP server"]
    rel1 --> test["Test release on GitHub"]
    test --> srv1["/rp server on the RP server"]
    srv1 --> check{"Right in game?"}
    check -- no --> push
    check -- yes --> pr["Pull request: development to master"]
    pr --> rel2["/rp release on a main server"]
    rel2 --> srv2["/rp server on the main servers"]
    srv2 --> players["Players get the pack"]

You push your work to the pack's development branch.
/rp release <pack> <tag> <title> on the RP server builds the zips from what GitHub has on development, and publishes them as a GitHub release in a test repository.
/rp server <pack> <tag> <Minecraft version> points the RP server at that release. Only then do players there get it.
When the pack looks right, a pull request from development into master brings it to production, where the same two commands run on a main server.

/rp release and /rp server need the permission architect.resourcePackAdmin (part of MCME-Architect).

The packs today

As of November 2026, from the packs' GitHub releases. Staff type the start of the pack's name in the /rp commands.

Pack	Typed as	Kind	Repository
Human	`h`	Sodium	`MCME/RP-Human`
Mordor	`m`	Sodium	`MCME/RP-Mordor`
Paths of the Dead	`p`	Sodium	`MCME/RP-PathOfTheDead`
Dwarven	`d`	vanilla-only	`MCME/RP-Dwarven`
Rohan	`r`	vanilla-only	`MCME/RP-Rohan`
Lothlorien	`l`	vanilla-only	`MCME/RP-Lothlorien`

Every pack except Rohan carries the shader base and serves Minecraft 26.2 and 26.3 from one zip, through a mc26_3 overlay (see The shader base). Rohan's last release, v1.3.10 from February 2026, predates the shader base.

Where to start

I want to…	Read
Lay out a new pack, or check that mine is right	Pack repository
See what my pack will look like without mods, on my own computer	Pack repository: try the conversion
Understand exactly what the converter does to a Sodium pack	How the conversion works
Add a shader feature, or understand the shaders in my pack	The shader base
Release a pack, or know what `/rp release` does	The release pipeline
Fix a failed release, a warning, or a pack players don't get	Troubleshooting
Add a pack to the server's release automation	Resource pack server (operators only)

The same material, written for the repository, is in ResourcePackScripts' docs/ folder and its README.