This project is DEPRECATED. Please switch to official (mojang) mappings if you want parity between mod APIs.

What is this?

This service provides custom mappings for use when creating forge mods, that use the yarn mapping data. Two artifacts are published daily:

• Yarn mappings on top of MCP (srgs) for the latest stable Yarn version (currently 1.16.1). If the two versions are the same, this will be skipped
• A set of mixed mappings, which use 1.14.3 MCP mappings applied to the latest (currently 1.16.1) srgs, with yarn names filling in as many unnamed members as possible. This is the set you most likely want.

Additionally, a stable channel of Yarn on top of MCP srgs is published for the latest stable version of MCP.

They can be used by adding my maven (https://maven.tterrag.com/) to your gradle repositories, and adding -yarn (for yarn mappings) or -mixed (for mixed mappings) suffix to the snapshot version (e.g. 20240418-mixed-1.16.1). So overall, it should look like this:

repositories {
    maven {
        url "https://maven.tterrag.com/"
    }
}

minecraft {
    mappings channel: 'snapshot', version: '20240418-mixed-1.16.1'
    ...

For stable 1.16.1 yarn mappings, use the channel 'stable' with the version 'yarn-1.16.1'.

Why?

MCP does not currently have mappings released for 1.16.1, so this fills the gap until those are completed so that modders can work on 1.16.1 forge mods without all the new fields/methods being unnamed. Additionally, due to the legal issues surrounding the official mojang mappings, I wanted to give forge modders the choice to use an alternative mapping set entirely.