tutorial:migratemappings
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| tutorial:migratemappings [2022/07/08 19:20] – external edit 127.0.0.1 | tutorial:migratemappings [2025/11/16 00:02] (current) – cassiancc | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Updating Yarn mappings | + | ~~REDIRECT> |
| - | Loom allows semi-automatic updating of the mappings used in a Java codebase. Due to frequent changes in Yarn, this can be a useful tool for keeping a codebase up-to-date with the newest changes. | + | ====== Migrating to Yarn or Mojang Mappings |
| - | **Note: | + | Loom allows semi-automatic updating of the mappings used in a Java codebase. |
| - | ===== Loom 0.2.6 and above ===== | + | Loom does not support migrating code written in Kotlin. [[https:// |
| - | Say you want to migrate from 1.16.5 to 1.17.1. | + | **Note:** Loom 1.13 is required for this process |
| - | - Go [[https:// | + | |
| - | - Run the command in the root of your Gradle project. | + | ===== Migrating to Mojang Mappings ===== |
| + | |||
| + | These instructions cover migration from Yarn to Mojang Mappings. | ||
| + | |||
| + | - You'll need a command | ||
| + | - Run the command in the root of your Gradle project, either through the terminal, or by adding it as a run configuration in IntelliJ Idea. | ||
| - Your migrated sources will appear in '' | - Your migrated sources will appear in '' | ||
| - Copy the sources from '' | - Copy the sources from '' | ||
| - | - Update | + | - If you are coming from Yarn, you can now replace |
| - Refresh the Gradle project in your IDE. | - Refresh the Gradle project in your IDE. | ||
| - Check and update any Mixin targets that may be outdated. | - Check and update any Mixin targets that may be outdated. | ||
| - | === Additional customization === | + | Your dependencies section should now contain this: |
| - | * Specify from where to take your Java files with '' | + | |
| - | * Specify where to output the remapped source with '' | + | |
| - | * Specify a custom place to retrieve the mappings from with '' | + | |
| - | === Reporting issues === | ||
| - | Loom uses [[https:// | ||
| - | ===== Loom 0.2.2-0.2.5 ===== | + | dependencies { |
| + | [...] | ||
| + | mappings loom.officialMojangMappings() | ||
| + | } | ||
| - | Some assembly required. | ||
| - | - Figure out your target mappings version. For example, " | ||
| - | - Make sure the mappings for this version get created. This is the hacky part, as currently the only way to do it is to edit the " | ||
| - | - Run the following magical wizardry command: '' | ||
| - | * " | ||
| - | * " | ||
| - | * " | ||
| - | - Copy the remapped source code to the input directory, if everything' | ||
| - | - Hope for the best. | ||
| - | //Note: You may need to specify the full paths in quotes, try this if you get file not found issues.// | + | ===== Migrating |
| - | This should work across Minecraft versions as well, provided we haven't massively broken Intermediaries | + | These instructions cover migration from Mojang Mappings (or an older version of Yarn) to Yarn. |
| + | |||
| + | - Go [[https:// | ||
| + | - Run the command in the root of your Gradle project, either through the terminal, or by adding it as a run configuration in IntelliJ Idea. | ||
| + | - Your migrated sources will appear in '' | ||
| + | - Copy the sources from '' | ||
| + | - Update or add to your '' | ||
| + | - If you are coming from Mojang Mappings, you can now replace your mappings in your '' | ||
| + | - Refresh | ||
| + | - Check and update any Mixin targets that may be outdated. | ||
| + | |||
| + | Your dependencies section should now contain this, with the version of Yarn you are using specified in your '' | ||
| + | |||
| + | dependencies { | ||
| + | [...] | ||
| + | mappings " | ||
| + | } | ||
| + | |||
| + | === Migrating Split Sources === | ||
| + | |||
| + | At this time, users of split sources currently need to migrate their main source set with the process above, then do the process again, specifying the path to their client source set. As a reference, the command to migrate a client source set to Mojang Mappings is below. | ||
| + | |||
| + | |||
| + | migrateMappings --mappings " | ||
| + | |||
| + | === Additional customization === | ||
| + | * Specify from where to take your Java files with '' | ||
| + | * Specify where to output the remapped source with '' | ||
| + | * Specify a custom place to retrieve the mappings from with '' | ||
| + | |||
| + | === Reporting issues === | ||
| + | Loom uses a fork of [[https:// | ||
tutorial/migratemappings.1657308044.txt.gz · Last modified: 2022/07/08 19:20 by 127.0.0.1