Differences

This shows you the differences between two versions of the page.

--- tutorial:migratemappings [2025/10/31 18:21] – Rewrite to better clarify how to handle Mojang Mappings cassiancc
+++ tutorial:migratemappings [2025/10/31 21:04] (current) – typo cassiancc
@@ Line 1: / Line 1: @@
+:!: //A more thorough documentation of the process of migrating mappings, along with better, specific tooling is currently planned for the near future in order to help the transition into the non-obfuscated MC versions. This page will likely redirect to the proper documentation once it is in a satisfying state.//
 ====== Migrating to Yarn or Mojang Mappings in a Java codebase ======
-Loom allows semi-automatic updating of the mappings used in a Java codebase. This can be a useful tool for users wishing to keep their codebase up-to-date with the new changes in Yarn, or for users wishing to change to different mappings, including Mojang's own mappings.
+Loom allows semi-automatic updating of the mappings used in a Java codebase. This can be a useful tool for users wishing to keep their codebase up-to-date with the new changes in Yarn, or for users wishing to change to different mappings, including Mojang's own mappings. For more information, check out the dedicated [[tutorial:mappings|Mappings]] page.
-Loom does not support migrating from Kotlin. [[https://github.com/Deftu/ReplayMod-Remap|Third party tools]] are available.
+Loom does not support migrating code written in Kotlin. [[https://github.com/Deftu/ReplayMod-Remap|Third party tools]] are available.
 **Note:** This automated process does not yet handle Mixins or reflection. Updated tooling is currently in the works that will fix these errors. This tooling will be available before the mandatory switch to Mojang names in a future version of Minecraft.
@@ Line 12: / Line 14: @@
 These instructions cover migration from Yarn to Mojang Mappings.
-  - You'll need a command to migrate your mappings to Moajng Mappings, for example ''gradlew migrateMappings %%--%%mappings %%"%%net.minecraft:mappings::1.21.10%%"%%''. Replace ''1.21.10'' with the version of Minecraft you are migrating from. This must be the same version of Minecraft you are currently running. DO NOT modify your ''gradle.properties'' or ''build.gradle'' yet.
+  - You'll need a command to migrate your mappings to Mojang Mappings, for example ''gradlew migrateMappings %%--%%mappings %%"%%net.minecraft:mappings:1.21.10%%"%%''. Replace ''1.21.10'' with the version of Minecraft you are migrating from. This must be the same version of Minecraft you are currently running. DO NOT modify your ''gradle.properties'' or ''build.gradle'' yet.
   - 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 ''remappedSrc''. Verify that the migration produced valid migrated code.
@@ Line 39: / Line 41: @@
   * Specify where to output the remapped source with ''%%--%%output path/to/output''. Default: 'remappedSrc'. You can use ''src/main/java'' here to avoid having to copy the remapped classes, but make sure you have a backup.
   * Specify a custom place to retrieve the mappings from with ''%%--%%mappings some_group:some_artifact:some_version:some_qualifier''. Default: ''net.fabricmc:yarn:<version-you-inputted>:v2''. Use ''net.minecraft:mappings:<minecraft-version>'' to migrate to official Mojang mappings.
-For more information, check out the dedicated [[tutorial:mappings|Mappings]] page.
 === Reporting issues ===
 Loom uses a fork of [[https://github.com/FabricMC/Mercury|Mercury]] to remap Java source code, for problems with remapping please report issues to its [[https://github.com/FabricMC/Mercury/issues|issue tracker]].