Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

[SOLVED] Mod setup issues: "Could not find mapped snapshot"


Hamster_Furtif
 Share

Recommended Posts

EDIT: SOLVED BY DELETING THE  .gradle DIRECTORY AND REFRESHING THE GRADLE PROJECT

 

Hello, I'm trying to set up a mod in 1.15.2 using IntelliJ.

 

To set it up, I've opened the build.gradle file from IntelliJ as a project, then ran the getIntellijRuns  from the gradle pannel, then ran the gradle build command into the terminal.

 

Here is a pastebin of the terminal output:

https://pastebin.com/UJqUtNHW

 

I believe this is the most relevant part :

* What went wrong:
Could not resolve all files for configuration ':compileClasspath'.
> Could not find net.minecraftforge:forge:1.15.2-31.1.0_mapped_snapshot_20200223-1.15.1.
  Searched in the following locations:
    - file:/C:/Users/HamsterFurtif/.gradle/caches/forge_gradle/bundeled_repo/net/minecraftforge/forge/1.15.2-31.1.0_mapped_snapshot_20200223-1.15.1/forge-1.15.2-31.1.0_mapped_snapshot_20200223-1.15.1.pom
    - file:/C:/Users/HamsterFurtif/.gradle/caches/forge_gradle/bundeled_repo/net/minecraftforge/forge/1.15.2-31.1.0_mapped_snapshot_20200223-1.15.1/forge-1.15.2-31.1.0_mapped_snapshot_20200223-1.15.1.jar
    - https://files.minecraftforge.net/maven/net/minecraftforge/forge/1.15.2-31.1.0_mapped_snapshot_20200223-1.15.1/forge-1.15.2-31.1.0_mapped_snapshot_20200223-1.15.1.pom
    - https://files.minecraftforge.net/maven/net/minecraftforge/forge/1.15.2-31.1.0_mapped_snapshot_20200223-1.15.1/forge-1.15.2-31.1.0_mapped_snapshot_20200223-1.15.1.jar
    - https://libraries.minecraft.net/net/minecraftforge/forge/1.15.2-31.1.0_mapped_snapshot_20200223-1.15.1/forge-1.15.2-31.1.0_mapped_snapshot_20200223-1.15.1.jar
    - https://repo.maven.apache.org/maven2/net/minecraftforge/forge/1.15.2-31.1.0_mapped_snapshot_20200223-1.15.1/forge-1.15.2-31.1.0_mapped_snapshot_20200223-1.15.1.pom
    - https://repo.maven.apache.org/maven2/net/minecraftforge/forge/1.15.2-31.1.0_mapped_snapshot_20200223-1.15.1/forge-1.15.2-31.1.0_mapped_snapshot_20200223-1.15.1.jar
  Required by:
      project :

 

This is what it looks like on the gradle pannel:

image.png.937d75985fcbc889e3ba9309eecf9d1c.png

 

When I go to File>Project Structure>Libraries, it also tells me that the mapped snapshots lib cannot be found.

 

I've seen a few other forum posts with the same issue, but none of them could help me solve this issue. I've tried (with no success):

-to update my JDK (1.8 to 1.12)

-to edit the mappings version field in the build.gradle file, using the latest MPCBot release

mappings channel: 'snapshot', version: '20200223-1.15.1'

 

I'd be really grateful if someone could help me sort this out.

Edited by Hamster_Furtif
Link to comment
Share on other sites

Thanks for your suggestion, but unfortunately this didn't work. The issue remains even when restarting from a clean mdk, but only with forge 1.15.

However I noticed that the directory gradle is looking for does not exists:

C:/Users/HamsterFurtif/.gradle/caches/forge_gradle/bundeled_repo/net/minecraftforge/forge/1.15.2-31.1.0_mapped_snapshot_20200223-1.15.1/

But this one exists:

C:\Users\HamsterFurtif\.gradle\caches\forge_gradle\minecraft_user_repo\net\minecraftforge\forge

and contains the files gradle is looking for.  It is the one that is used by my 1.14 project, but I can see the 1.15 files were downloaded there.

I guess what I need to do is to force gradle to search in there but I have no idea how to do that. I'm also curious as to why it works fine with 1.14 but not 1.15.

Edited by Hamster_Furtif
Some of the stuff I had written was incorrect
Link to comment
Share on other sites

It sounds like you interrupted a mapping download. Try this in Powershell:

Remove-Item -Recurse -Path "$Env:USERPROFILE/.gradle/caches/forge_gradle/maven_downloader/de/oceanlabs/mcp/mcp_snapshot/20200223-1.15.1"

This will delete the cached mapping zip (which is apparently corrupted) and its hash.

This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy.

 

As the most common issue I feel I should put this outside the main bulk:

The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge.

If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan.

 

For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety.

Spoiler

Logs (Most issues require logs to diagnose):

Spoiler

Please post logs using one of the following sites (Thank you Lumber Wizard for the list):

https://gist.github.com/100MB Requires member (Free)

https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$)

https://hastebin.com/: 400KB

Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.

 

What to provide:

...for Crashes and Runtime issues:

Minecraft 1.14.4 and newer:

Post debug.log

Older versions:

Please update...

 

...for Installer Issues:

Post your installer log, found in the same place you ran the installer

This log will be called either installer.log or named the same as the installer but with .log on the end

Note for Windows users:

Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension

 

Where to get it:

Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs.

 

Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:

Spoiler
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it).
  4. Now launch the pack through that profile and follow the "Mojang Launcher" instructions above.

Video:

Spoiler

 

 

 

or alternately, 

 

Fallback ("No logs are generated"):

If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft

 

Server Not Starting:

Spoiler

If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output.

 

Reporting Illegal/Inappropriate Adfocus Ads:

Spoiler

Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad.

Lex will need the Ad ID contained in that URL to report it to Adfocus' support team.

 

Posting your mod as a GitHub Repo:

Spoiler

When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub.

When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. Run the following commands:
    1. git init
    2. git remote add origin [Your Repository's URL]
      • In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git
    3. git fetch
    4. git checkout --track origin/master
    5. git stage *
    6. git commit -m "[Your commit message]"
    7. git push
  4. Navigate to GitHub and you should now see most of the files.
    • note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

Link to comment
Share on other sites

  • 2 months later...

The solution forgets to mention that you may still have a gradle daemon running. You *must* stop the daemon first, then delete the caches and try a new build. That explains why you may still be running into issues even after a refresh.

Edited by Stragulus
Link to comment
Share on other sites

  • 2 months later...

I tried the same thing by deleting the .gradle directory and restarting but i still got the errors.

https://www.reddit.com/r/Minecraft/comments/ic0ll3/plz_help_so_i_was_trying_to_use_intellij_for/

U may use this link to look at an image to my problem. I am really new to IntelliJ(like i dont even know what gradle is) and i really want to mod but this error is happening and ur edited solution doesnt work for me.

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.

Guest
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.

 Share



×
×
  • Create New...

Important Information

By using this site, you agree to our Privacy Policy.