Jump to content
View in the app

A better way to browse. Learn more.
Forge Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Currently supported: All versions

Cant setup forge.

XlaytonPlz
in ForgeGradle

Featured Replies

Posted

Whenever I try to run "gradlew setupDecompWorkspace" it gives me this error consistently:

 

Exception in thread "main" java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.gradle.wrapper.BootstrapMainStarter.start(BootstrapMainStarter.java:30)
        at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:127)
        at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61)
Caused by: java.lang.NoClassDefFoundError: org/gradle/api/internal/classpath/ModuleRegistry
        at org.gradle.launcher.GradleMain.main(GradleMain.java:23)
        ... 7 more
Caused by: java.lang.ClassNotFoundException: org.gradle.api.internal.classpath.ModuleRegistry
        at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
        ... 8 more

 

I tried to search around for other issues similar, but I cant find anything.

Edited by XlaytonPlz

  • Quote

    Is this with Forge's MDK or are you contributing to an existing mod?

    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]

     

  • Quote
    • Author
    2 hours ago, Oen44 said:

    Post details about java version etc.

    JDK: 1.8.0_181

    JRE 1.8.0_181

    Forge: 1.12.2-14.23.4.2705

    Edited by XlaytonPlz

  • Quote

    What's your OS?

    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]

     

  • Quote

    When you run the command does it say anything about downloading gradle?

    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]

     

  • Quote
    • Author
    3 minutes ago, DaemonUmbra said:

    When you run the command does it say anything about downloading gradle?

    Everything that it says is in the OP.

    I ran it again to make sure.

    Also, just to cover my own bases, I did cd to the right folder.

    I also tried this command before with Java 10.x before, and got the same message

    Edited by XlaytonPlz

  • Quote

    I'm actually not sure if this will make a difference, but try gradlew.bat instead of just gradlew, and try it alone first

    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]

     

  • Quote
    • Author
    1 minute ago, DaemonUmbra said:

    I'm actually not sure if this will make a difference, but try gradlew.bat instead of just gradlew, and try it alone first

    Huh. the gradlew batch file is kicking up the errors alone. Now im even more confused. Oof

  • Quote

    Have you tried getting a fresh MDK?

    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]

     

  • Quote
    • Author
    2 minutes ago, DaemonUmbra said:

    Have you tried getting a fresh MDK?

    Twice. 

    EDIT: Tried again, same problem. Thrice.

    Edited by XlaytonPlz

  • Quote

    If you've been using the same folder for all this try deleting the .gradle folder and there will also be one in your user folder, delete that as well

    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]

     

  • Quote
    • Author
    2 minutes ago, DaemonUmbra said:

    If you've been using the same folder for all this try deleting the .gradle folder and there will also be one in your user folder, delete that as well

    All my attempts have been in different folders.

    I tried deleting gradle folders, and it caused it failed out twice before downloading gradle-2.14-bin.zip

    downloading still, edit when done

  • Quote
    • Author

    OK, so Im pretty sure the redownload worked. A download is going, but my internet is slow. One last update coming for possible confirmation once actually done.

  • Quote

    • 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...
    Go to topic listing

    Important Information

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

    I accept

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.