Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Currently Supported: 1.16.X (Latest) and 1.15.X (LTS)

issue with installed forge version not showing in insilations

airwake

By airwake,
in Support & Bug Reports

 Share Followers 0

Recommended Posts

DaemonUmbra

DaemonUmbra 543

Posted
Posted

1.8 is no longer supported on this forum.

Please update to a modern version of Minecraft to receive support.

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.

 

Twitch Launcher: If you are using the Twitch Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Twitch'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 post
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Followers 0
Go to topic listing


  • Recently Browsing

    No registered users viewing this page.

  • Posts

    • grepper
      How to create fat jar after reobfJar?

      By grepper · Posted

      I am wrong. Looks like shadowJar runs on assemble. I will try it.
    • grepper
      How to create fat jar after reobfJar?

      By grepper · Posted

      When does shadowJar run? I thought it runs at the same time the jar task runs, which is before reobfJar. I need it to run after reobfJar.
    • diesieben07
      How to create fat jar after reobfJar?

      By diesieben07 · Posted

      You should probably use the Shadow plugin.
    • grepper
      How to create fat jar after reobfJar?

      By grepper · Posted

      Hi, I am trying to get HikariCP bundled with my mod as a one fat jar. But there is a problem where HikariCP causes reobfJar to fail with InvalidArgumentException, and I'm not sure why. Here is my gradle code right now (I left out a lot of stuff which I don't think matters):   configurations { embed } dependencies { minecraft 'net.minecraftforge:forge:1.16.5-36.1.0' embed group: 'com.zaxxer', name: 'HikariCP', version: '4.0.3' compileOnly group: 'com.ea.async', name: 'ea-async', version: '1.2.3' } jar { from configurations.embed.collect{ it.isDirectory() ? it : zipTree(it) } manifest { attributes([ "Specification-Title": "examplemod", "Specification-Vendor": "examplemodsareus", "Specification-Version": "1", // We are version 1 of ourselves "Implementation-Title": project.name, "Implementation-Version": "${version}", "Implementation-Vendor" :"examplemodsareus", "Implementation-Timestamp": new Date().format("yyyy-MM-dd'T'HH:mm:ssZ") ]) } } jar.finalizedBy('reobfJar')   As I understand, this is the current order of events: `jar` task to run, which will bundle all the dependencies marked with `embed`, which will create the fat jar `reobfJar` will run on that fat jar. Would I would like to do instead is this order of events: `jar` task to run, but no fat jar is created at this time. `reobfJar` will run on the output of `jar`. A new task runs, which will take the output of `reobfJar` and combine it with the dependencies marked with `embed` to create the one fat jar   I think the code would look something like this:   jar { manifest { attributes([ "Specification-Title": "examplemod", "Specification-Vendor": "examplemodsareus", "Specification-Version": "1", // We are version 1 of ourselves "Implementation-Title": project.name, "Implementation-Version": "${version}", "Implementation-Vendor" :"examplemodsareus", "Implementation-Timestamp": new Date().format("yyyy-MM-dd'T'HH:mm:ssZ") ]) } } jar.finalizedBy('reobfJar') task bundle(type: Jar) { manifest { attributes 'Main-Class': 'com.gluecode.fpvdrone.server.Main' } from "build/libs/modid-1.0.jar" from configurations.embed.collect{ it.isDirectory() ? it : zipTree(it) } } The problems I have with the above is: I have to run `./gradlew bundle` after running `./gradlew buildNeeded`. And I'd like to just run 1 command. It doesn't work because it results in an invalid mod jar. I'm am still learning gradle. Can anyone help me?
    • SpaceFlier
      Forge Installer Not Opening

      By SpaceFlier · Posted

      Thanks a lot. It worked!

  • Topics

  • Who's Online (See full list)

×
×
  • Create New...

Important Information

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

  I accept