Jump to content
Search the Forums BEFORE making a new post.
Currently supported: All versions

Unable to build example mod (1.14.4)

mbh333

By mbh333
in Modder Support

 Share

Recommended Posts

mbh333 Tree Puncher

mbh333

Posted
Posted (edited)

---

UPDATE:

 

As of August 01 I've managed to resolve this issue (as described in the thread below), but after building the mod I am still unable to test it in the client.
I'm compiling a list of related threads here, as this seems to be an unresolved issue for several people.

 

The following threads are related to the original issue of finding the mapped snapshot:

[July 20] Could not find mapped snapshot

[July 31] gradle genIntellijRuns does not supply 1.14.4 forge as external library

[July 31] Can't Download Forge, failing on :compileJava

 

The following threads are related to the ongoing issue of being unable to test the mod:

[August 01] Cannot Load or Test Mod (1.14.4)

 

---

ORIGINAL POST:

 

Hi all, newcomer here. I've done a bit of research on this and can't find any answers.

After downloading and extracting the mdk, I've followed the steps found here but whenever I try to run gradlew build I run into this error:

  

* What went wrong:                                                                                                                                                                                                                Could not resolve all files for configuration ':compileClasspath'.
> Could not find net.minecraftforge:forge:1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3.
  Searched in the following locations:
    - file:/C:/Users/[username]/.gradle/caches/forge_gradle/bundeled_repo/net/minecraftforge/forge/1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3/forge-1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3.pom
    - file:/C:/Users/[username]/.gradle/caches/forge_gradle/bundeled_repo/net/minecraftforge/forge/1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3/forge-1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3.jar
    - https://files.minecraftforge.net/maven/net/minecraftforge/forge/1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3/forge-1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3.pom
    - https://files.minecraftforge.net/maven/net/minecraftforge/forge/1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3/forge-1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3.jar
    - https://libraries.minecraft.net/net/minecraftforge/forge/1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3/forge-1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3.jar - https://repo.maven.apache.org/maven2/net/minecraftforge/forge/1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3/forge-1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3.pom
    - https://repo.maven.apache.org/maven2/net/minecraftforge/forge/1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3/forge-1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3.jar
  Required by:
      project :

 

The first problem I identified was that the forge_gradle directory did not contain a folder named "bundeled_repo". It did however contain something called "minecraft_user_repo", which contained the rest of the file path and the .pom file that gradle was searching for. I assume this is an error in the installation, so I made a copy of the "minecraft_user_repo" folder and renamed it "bundeled_repo". I tried building the project again, but received the same error as above.

I have deleted the entire project folder and re-extracted the mdk, multiple times, with no luck. For what it's worth, I have installed and run Forge version 1.14.4-28.0.24 and I'm using eclipse with the 8u221 version of both the JDK and JRE.

As far as I can tell this seems like an issue with the 1.14.4 version of either forge or the mdk, but I can't find any information, and I am totally new to modding so I'm not sure how to proceed from here.

 

Any help would be appreciated, cheers!

 

Edited by mbh333
DaemonUmbra Reality Controller

DaemonUmbra

Posted
Posted

Yeah the docs need to be updated.

Don't mess about in the Gradle cache.

 

What IDE are you using?

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]

 

mbh333 Tree Puncher

mbh333

Posted
  • Author
Posted

I'm using Eclipse 2019-03 (4.11.0)

 

All I've done is:

  • run the gradlew eclipse command in my project folder
  • import the project folder into eclipse
  • change the group and archivesBaseName fields in the build.gradle file
  • run gradlew build from the command line

 

Worth noting, I just tried running gradlew eclipse on a new extraction of the mdk files, and I noticed this in the console, towards the end: 

MinecraftUserRepo: Failed to get Minecraft Joined SRG. Should not be possible.
Could not resolve: net.minecraftforge:forge:1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3

 

This is followed by a warning about deprecated gradle features making it incompatible with Gradle 5.0, and then the "build successful" message.

mbh333 Tree Puncher

mbh333

Posted
  • Author
Posted (edited)

This issue has finally been resolved, after I tried the following:

  • re-install the JRE and JDK for version 1.8.0_221
  • remove any newer versions of the JDK that were previously installed
  • restart the computer

 

I still have no idea what was causing it, and I have seen a few other instances of people running into the same error, so I'm editing the original post to keep track of these threads. If it is indeed related to the JDK, then it would be good if the error message made that clear, or if there was a clearly documented solution somewhere for these sorts of basic setup issues.

Edited by mbh333
Clarifying solution.
  • 6 months later...
MC_Wolf Newbie

MC_Wolf

Posted
Posted (edited)

i solve this problem. i think look at wrong place

the gradle is searching for "tools.jar" but it search in wrong place instead in your jdk installation folder the gradle search in your jre installation folder

the main problem is not 

> Could not find net.minecraftforge:forge:1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3.
  Searched in the following locations:
    - file:/C:/Users/[username]/.gradle/caches/forge_gradle/bundeled_repo/net/minecraftforge/forge/1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3/forge-1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3.pom
    - file:/C:/Users/[username]/.gradle/caches/forge_gradle/bundeled_repo/net/minecraftforge/forge/1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3/forge-1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3.jar
    - https://files.minecraftforge.net/maven/net/minecraftforge/forge/1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3/forge-1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3.pom
    - https://files.minecraftforge.net/maven/net/minecraftforge/forge/1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3/forge-1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3.jar
    - https://libraries.minecraft.net/net/minecraftforge/forge/1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3/forge-1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3.jar - https://repo.maven.apache.org/maven2/net/minecraftforge/forge/1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3/forge-1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3.pom
    - https://repo.maven.apache.org/maven2/net/minecraftforge/forge/1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3/forge-1.14.4-28.0.24_mapped_snapshot_20190719-1.14.3.jar

but the main problem is the gradle cannot find the tools.jar

 

step to fix it

1. copy all file in [your jdk installation folder]\lib\*.* to [your jre installation folder]\lib\  (i recommended to copy all not only "tools.jar"(who  know it depent other library))

2. restart cmd

3. run your gradle task

and it maybe fixed

 

story how i solved it:

one day i run a minecraft forge gradle task and it results BUILD UNSUCCESFUL error an i read everything that show in the cmd from when i type the "gradlew build" command to the end and i find the main cause of the problem is the gradle cannot find the tools.jar(to find this i set screen buffer height to 9000 and width 167) and i have installed the java JDK and i think it maybe search in my JRE folder to test if this true i copy all files and folder in [jdk installation fold]\lib\*.* to [jre installation folder]\lib\ and it work and i post this to this forum

Edited by MC_Wolf
i forget to check all the error from start to the end and i also look at wrong place i just realize it

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

×
 Share
Go to topic listing

Announcements



×
×
  • Create New...

Important Information

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

  I accept