Jump to content

[1.15.2] Custom mappings


Recommended Posts

I have custom mappings. I have a repository with them. I tryed to attach them:

    mappings channel: 'custom', version: 'com.github.GoogeTan:TheMappings:Tag'
    accessTransformer = file('src/main/resources/META-INF/accesstransformer.cfg')
            workingDirectory project.file('run')
            property 'forge.logging.markers', 'SCAN,REGISTRIES,REGISTRYDUMP'
            property 'forge.logging.console.level', 'debug'

But it shouts:

A problem occurred configuring root project 'PhoenixProject'.
> Supplied String module notation 'net.minecraftforge:forge:1.15.2-31.2.47_mapped_custom_com.github.GoogeTan:TheMappings:Tag_at_904f7754f2116b78834cf8ff88239b5b038624fc' is invalid. Example notations: 'org.gradle:gradle-core:2.2', 'org.mockito:mockito-core:1.9.5:javadoc'.

What i sould do?

Link to comment
Share on other sites

On 6/14/2021 at 12:08 PM, WildTan said:

What i sould do?

Note that I am no expert on mappings, and I think generally it is best to use the same mappings as most other people use to make life easier for everybody. However, with that said, this should work:

1. Add this to your build.gradle to create a local maven repo on your computer:

repositories {
    maven {
        url "file:///${project.projectDir}/mappings"

2. Change back the mappings channel (the mappings channel is hardcoded to use 'official', 'snapshot' and 'stable' so you have to use one of those):

mappings channel: 'snapshot', version: 'vemerion-mappings'

You can of course change 'vemerion-mappings' to something else but then you have to change it in the mappings repo as well in the next few steps

3. Create the file structure 'mappings/de/oceanlabs/mcp/mcp_snapshot/vemerion-mappings/' in your mod project folder

4. Inside the file structure you just created, create a zip file named 'mcp_snapshot-vemerion-mappings.zip', that should contain the fields.csv and methods.csv files etc

5. Run ./gradlew clean and ./gradlew cleanEclipse

6. Run ./gradlew genEclipseRuns and ./gradlew eclipse

7. If gradle complains about duplicate mappings then everything will probably fail and you have to update your mappings files and redo the process

8. Import the project into Eclipse

9. Your custom mappings should now work

Hope this helps! As a last word of caution, I just want to reiterate that IMO it is probably best to stick with the normal MCP or Mojang mappings.

  • Like 2
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...

Important Information

By using this site, you agree to our Terms of Use.