Forge 1.14.3 - is not showing up in the "version" section - Support & Bug Reports

Posted July 4, 20196 yr

I've tried so many versions of Forge 1.14.3, but it keeps not showing up when I try to select the version, it shows up ONLY the old versions of Forge (for example the 1.12.2) and the vanilla ones.

To be honest I don't know what I should do, I deleted and reinstalled the folders, I can't use the latest versions (27.0.23 and 27.0.22) because for some reason it pops up an error message during the installation, and if I try to install older versions like 27.0.2 it won't show up in the version section...

Also this the error message when I try to install the latest versions

Screenshot_1.png.be864926749b4a9adcddc222a46a9a33.png

And this is the log file:

JVM info: Oracle Corporation - 1.8.0_211 - 25.211-b12
java.net.preferIPv4Stack=true
Extracting json
Extracting json
Considering minecraft client jar
Considering minecraft client jar
Downloading libraries
Downloading libraries
Considering library net.minecraftforge:forge:1.14.3-27.0.23
File exists: Checksum validated.
Considering library org.ow2.asm:asm:6.2
File exists: Checksum validated.
Considering library org.ow2.asm:asm-commons:6.2
File exists: Checksum validated.
Considering library org.ow2.asm:asm-tree:6.2
File exists: Checksum validated.
Considering library cpw.mods:modlauncher:2.1.5
File exists: Checksum validated.
Considering library cpw.mods:grossjava9hacks:1.1.0
File exists: Checksum validated.
Considering library net.minecraftforge:accesstransformers:0.16.0-shadowed
File exists: Checksum validated.
Considering library net.minecraftforge:eventbus:0.10.2-service
File exists: Checksum validated.
Considering library net.minecraftforge:forgespi:0.13.0
File exists: Checksum validated.
Considering library net.minecraftforge:coremods:0.6.3-milestone.0.2+e9179e4
File exists: Checksum validated.
Considering library net.minecraftforge:unsafe:0.2.0
File exists: Checksum validated.
Considering library com.electronwill.night-config:core:3.6.0
File exists: Checksum validated.
Considering library com.electronwill.night-config:toml:3.6.0
File exists: Checksum validated.
Considering library org.jline:jline:3.9.0
File exists: Checksum validated.
Considering library org.apache.maven:maven-artifact:3.6.0
File exists: Checksum validated.
Considering library net.jodah:typetools:0.6.0
File exists: Checksum validated.
Considering library java3d:vecmath:1.5.2
File exists: Checksum validated.
Considering library org.apache.logging.log4j:log4j-api:2.11.2
File exists: Checksum validated.
Considering library org.apache.logging.log4j:log4j-core:2.11.2
File exists: Checksum validated.
Considering library net.minecrell:terminalconsoleappender:1.1.1
File exists: Checksum validated.
Considering library net.sf.jopt-simple:jopt-simple:5.0.4
File exists: Checksum validated.
Considering library com.github.jponge:lzma-java:1.3
File exists: Checksum validated.
Considering library com.google.code.findbugs:jsr305:3.0.2
File exists: Checksum validated.
Considering library com.google.code.gson:gson:2.8.0
File exists: Checksum validated.
Considering library com.google.errorprone:error_prone_annotations:2.1.3
File exists: Checksum validated.
Considering library com.google.guava:guava:20.0
File exists: Checksum validated.
Considering library com.google.guava:guava:25.1-jre
File exists: Checksum validated.
Considering library com.google.j2objc:j2objc-annotations:1.1
File exists: Checksum validated.
Considering library com.nothome:javaxdelta:2.0.1
File exists: Checksum validated.
Considering library commons-io:commons-io:2.4
File exists: Checksum validated.
Considering library de.oceanlabs.mcp:mcp_config:1.14.3-20190624.152911@zip
File exists: Checksum validated.
Considering library net.md-5:SpecialSource:1.8.5
File exists: Checksum validated.
Considering library net.minecraftforge:binarypatcher:1.0.5
File exists: Checksum validated.
Considering library net.minecraftforge:forge:1.14.3-27.0.23:universal
File exists: Checksum validated.
Considering library net.minecraftforge:installertools:1.1.1
File exists: Checksum validated.
Considering library net.minecraftforge:jarsplitter:1.1.0
File exists: Checksum validated.
Considering library net.sf.jopt-simple:jopt-simple:4.9
File exists: Checksum validated.
Considering library net.sf.jopt-simple:jopt-simple:5.0.4
File exists: Checksum validated.
Considering library net.sf.opencsv:opencsv:2.3
File exists: Checksum validated.
Considering library org.checkerframework:checker-qual:2.0.0
File exists: Checksum validated.
Considering library org.codehaus.mojo:animal-sniffer-annotations:1.14
File exists: Checksum validated.
Considering library org.ow2.asm:asm-analysis:6.1.1
File exists: Checksum validated.
Considering library org.ow2.asm:asm-commons:6.1.1
File exists: Checksum validated.
Considering library org.ow2.asm:asm-tree:6.1.1
File exists: Checksum validated.
Considering library org.ow2.asm:asm:6.1.1
File exists: Checksum validated.
Considering library trove:trove:1.0.2
File exists: Checksum validated.
Created Temporary Directory: C:\Users\papa\AppData\Local\Temp\forge_installer654255554352378823
Created Temporary Directory: C:\Users\papa\AppData\Local\Temp\forge_installer654255554352378823
Extracting: /data/client.lzma
Building Processors
Building Processors
===============================================================================
MainClass: net.minecraftforge.installertools.ConsoleTool
Classpath:
C:\Users\papa\AppData\Roaming\.minecraft\libraries\net\minecraftforge\installertools\1.1.1\installertools-1.1.1.jar
C:\Users\papa\AppData\Roaming\.minecraft\libraries\net\md-5\SpecialSource\1.8.5\SpecialSource-1.8.5.jar
C:\Users\papa\AppData\Roaming\.minecraft\libraries\net\sf\jopt-simple\jopt-simple\5.0.4\jopt-simple-5.0.4.jar
C:\Users\papa\AppData\Roaming\.minecraft\libraries\com\google\code\gson\gson\2.8.0\gson-2.8.0.jar
C:\Users\papa\AppData\Roaming\.minecraft\libraries\org\ow2\asm\asm-commons\6.1.1\asm-commons-6.1.1.jar
C:\Users\papa\AppData\Roaming\.minecraft\libraries\com\google\guava\guava\20.0\guava-20.0.jar
C:\Users\papa\AppData\Roaming\.minecraft\libraries\net\sf\opencsv\opencsv\2.3\opencsv-2.3.jar
C:\Users\papa\AppData\Roaming\.minecraft\libraries\org\ow2\asm\asm-analysis\6.1.1\asm-analysis-6.1.1.jar
C:\Users\papa\AppData\Roaming\.minecraft\libraries\org\ow2\asm\asm-tree\6.1.1\asm-tree-6.1.1.jar
C:\Users\papa\AppData\Roaming\.minecraft\libraries\org\ow2\asm\asm\6.1.1\asm-6.1.1.jar
Args: --task, MCP_DATA, --input, C:\Users\papa\AppData\Roaming\.minecraft\libraries\de\oceanlabs\mcp\mcp_config\1.14.3-20190624.152911\mcp_config-1.14.3-20190624.152911.zip, --output, C:\Users\papa\AppData\Roaming\.minecraft\libraries\de\oceanlabs\mcp\mcp_config\1.14.3-20190624.152911\mcp_config-1.14.3-20190624.152911-mappings.txt, --key, mappings
Task: MCP_DATA
Input: C:\Users\papa\AppData\Roaming\.minecraft\libraries\de\oceanlabs\mcp\mcp_config\1.14.3-20190624.152911\mcp_config-1.14.3-20190624.152911.zip
Output: C:\Users\papa\AppData\Roaming\.minecraft\libraries\de\oceanlabs\mcp\mcp_config\1.14.3-20190624.152911\mcp_config-1.14.3-20190624.152911-mappings.txt
Key: mappings
Extracting: config/joined.tsrg
===============================================================================
Cache:
C:\Users\papa\AppData\Roaming\.minecraft\libraries\net\minecraft\client\1.14.3\client-1.14.3-slim.jar Validated: 26e8580ce23d59759c2db41756a834a6df292313
C:\Users\papa\AppData\Roaming\.minecraft\libraries\net\minecraft\client\1.14.3\client-1.14.3-extra.jar Validated: e0a45cca33d23f63b149b4546978ee0e4d858167
Cache Hit!
===============================================================================
MainClass: net.md_5.specialsource.SpecialSource
Classpath:
C:\Users\papa\AppData\Roaming\.minecraft\libraries\net\md-5\SpecialSource\1.8.5\SpecialSource-1.8.5.jar
C:\Users\papa\AppData\Roaming\.minecraft\libraries\org\ow2\asm\asm-commons\6.1.1\asm-commons-6.1.1.jar
C:\Users\papa\AppData\Roaming\.minecraft\libraries\net\sf\jopt-simple\jopt-simple\4.9\jopt-simple-4.9.jar
C:\Users\papa\AppData\Roaming\.minecraft\libraries\com\google\guava\guava\20.0\guava-20.0.jar
C:\Users\papa\AppData\Roaming\.minecraft\libraries\net\sf\opencsv\opencsv\2.3\opencsv-2.3.jar
C:\Users\papa\AppData\Roaming\.minecraft\libraries\org\ow2\asm\asm-analysis\6.1.1\asm-analysis-6.1.1.jar
C:\Users\papa\AppData\Roaming\.minecraft\libraries\org\ow2\asm\asm-tree\6.1.1\asm-tree-6.1.1.jar
C:\Users\papa\AppData\Roaming\.minecraft\libraries\org\ow2\asm\asm\6.1.1\asm-6.1.1.jar
Args: --in-jar, C:\Users\papa\AppData\Roaming\.minecraft\libraries\net\minecraft\client\1.14.3\client-1.14.3-slim.jar, --out-jar, C:\Users\papa\AppData\Roaming\.minecraft\libraries\net\minecraft\client\1.14.3-20190624.152911\client-1.14.3-20190624.152911-srg.jar, --srg-in, C:\Users\papa\AppData\Roaming\.minecraft\libraries\de\oceanlabs\mcp\mcp_config\1.14.3-20190624.152911\mcp_config-1.14.3-20190624.152911-mappings.txt
Loading mappings
Loading mappings... 0%
Loading mappings... 10%
Loading mappings... 20%
Loading mappings... 30%
Loading mappings... 40%
Loading mappings... 50%
0 packages, 4696 classes, 17220 fields, 31208 methods
Remapping final jar
Remapping jar... 0%
Remapping jar... 10%
Remapping jar... 20%
Remapping jar... 30%
Remapping jar... 40%
Remapping jar... 50%
Remapping jar... 60%
Remapping jar... 70%
Remapping jar... 80%
Remapping jar... 90%
Remapping jar... 100%
===============================================================================
Cache:
C:\Users\papa\AppData\Roaming\.minecraft\libraries\net\minecraftforge\forge\1.14.3-27.0.23\forge-1.14.3-27.0.23-client.jar Validated: 285e3874143522da292b780bf60cd167732de1cc
Cache Hit!
===============================================================================
MainClass: net.minecraftforge.installertools.ConsoleTool
Classpath:
C:\Users\papa\AppData\Roaming\.minecraft\libraries\net\minecraftforge\installertools\1.1.1\installertools-1.1.1.jar
C:\Users\papa\AppData\Roaming\.minecraft\libraries\net\md-5\SpecialSource\1.8.5\SpecialSource-1.8.5.jar
C:\Users\papa\AppData\Roaming\.minecraft\libraries\net\sf\jopt-simple\jopt-simple\5.0.4\jopt-simple-5.0.4.jar
C:\Users\papa\AppData\Roaming\.minecraft\libraries\com\google\code\gson\gson\2.8.0\gson-2.8.0.jar
C:\Users\papa\AppData\Roaming\.minecraft\libraries\org\ow2\asm\asm-commons\6.1.1\asm-commons-6.1.1.jar
C:\Users\papa\AppData\Roaming\.minecraft\libraries\com\google\guava\guava\20.0\guava-20.0.jar
C:\Users\papa\AppData\Roaming\.minecraft\libraries\net\sf\opencsv\opencsv\2.3\opencsv-2.3.jar
C:\Users\papa\AppData\Roaming\.minecraft\libraries\org\ow2\asm\asm-analysis\6.1.1\asm-analysis-6.1.1.jar
C:\Users\papa\AppData\Roaming\.minecraft\libraries\org\ow2\asm\asm-tree\6.1.1\asm-tree-6.1.1.jar
C:\Users\papa\AppData\Roaming\.minecraft\libraries\org\ow2\asm\asm\6.1.1\asm-6.1.1.jar
Args: --task, DEOBF_REALMS, --map, C:\Users\papa\AppData\Roaming\.minecraft\libraries\de\oceanlabs\mcp\mcp_config\1.14.3-20190624.152911\mcp_config-1.14.3-20190624.152911-mappings.txt, --mc, C:\Users\papa\AppData\Roaming\.minecraft\versions\1.14.3\1.14.3.jar, --mcp, 20190624.152911
Task: DEOBF_REALMS
Map: C:\Users\papa\AppData\Roaming\.minecraft\libraries\de\oceanlabs\mcp\mcp_config\1.14.3-20190624.152911\mcp_config-1.14.3-20190624.152911-mappings.txt
MCP: 20190624.152911
Jar: C:\Users\papa\AppData\Roaming\.minecraft\versions\1.14.3\1.14.3.jar
Json: C:\Users\papa\AppData\Roaming\.minecraft\versions\1.14.3\1.14.3.json
Libs: C:\Users\papa\AppData\Roaming\.minecraft\libraries
Loading Json: C:\Users\papa\AppData\Roaming\.minecraft\versions\1.14.3\1.14.3.json
Failed to run processor: com.google.gson.JsonParseException:Error parsing arguments in version json. File is corrupt or its format has changed.
See log for more details.

Edited July 4, 20196 yr by WackoFurball6

July 4, 20196 yr

this error has persisted for me too, all forge updates excluding upto version .16 do not show up in the launcher, all the versions after that run the same error that OP has stated

July 4, 20196 yr

Delete the file it indicates, run the Minecraft Launcher, then try the installer again.

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

Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
Make a launcher profile targeting this version of Forge.
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).
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.

Open a command prompt (CMD, Powershell, Terminal, etc).
Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
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
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)
Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

July 4, 20196 yr

Author

What/Where is the file that I should delete?

July 4, 20196 yr

6 hours ago, WackoFurball6 said:

Loading Json: C:\Users\papa\AppData\Roaming\.minecraft\versions\1.14.3\1.14.3.json
Failed to run processor: com.google.gson.JsonParseException:Error parsing arguments in version json. File is corrupt or its format has changed.

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

Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
Make a launcher profile targeting this version of Forge.
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).
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.

Open a command prompt (CMD, Powershell, Terminal, etc).
Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
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
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)
Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

July 4, 20196 yr

Author

Nope, same error

July 4, 20196 yr

I get suspicious when people say "same error" because often times it's not and they can't tell the difference

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

Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
Make a launcher profile targeting this version of Forge.
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).
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.

Open a command prompt (CMD, Powershell, Terminal, etc).
Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
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
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)
Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

July 4, 20196 yr

Author

Yes yes, it is the same error, I compared it with the other one and they're the same

July 5, 20196 yr

Author

Since it doesn't seem to work, what should I do with the fact that older versions are not showing up? I'll try to be more specific, all the Forge versions AFTER 1.12.2 are not showing up anymore, what should I do?

July 6, 20196 yr

I have the same exact problem. All the versions from 1.12 and below are visible but 1.13 and 1.14 not. I also had this error earlier but I resolved it with dowloading an older version of Forge- 27.0.20.

July 6, 20196 yr

Please provide the file it mentions.

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

Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
Make a launcher profile targeting this version of Forge.
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).
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.

Open a command prompt (CMD, Powershell, Terminal, etc).
Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
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
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)
Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

July 6, 20196 yr

Author

Oh really? Could you send it? It would be amazing!

July 7, 20196 yr

Author

Actually... I was talking to Akiko, but no problem.

Here is the file

1.14.3.json

July 7, 20196 yr

https://files.minecraftforge.net/maven/net/minecraftforge/forge/index_1.14.3.html view all versions and download installer 27.02.21 or any below really works and the error doesn't occur. But versions in the laucher above 1.12 are still not visible for me.

July 7, 20196 yr

Author

27.02.21? Sorry but there isn't a file named like this, there is only 27.0.21

July 7, 20196 yr

Oh yes, typo, sorry.

July 9, 20196 yr

What launcher are you using? Please provide a screenshot.

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

Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
Make a launcher profile targeting this version of Forge.
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).
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.

Open a command prompt (CMD, Powershell, Terminal, etc).
Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
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
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)
Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

July 9, 20196 yr

Author

I'm using Shiginima Launcher SE v4200, what kind of screenshot do you need? Can you be more specific? Thanks

July 9, 20196 yr

User was banned for using a cracked launcher.

Buy the game.

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

Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
Make a launcher profile targeting this version of Forge.
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).
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.

Open a command prompt (CMD, Powershell, Terminal, etc).
Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
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
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)
Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

Sign In

Forge 1.14.3 - is not showing up in the "version" section

Featured Replies

Posts

java.lang.RuntimeException: null error

java.lang.RuntimeException: null error

java.lang.RuntimeException: null error

orbital strike cannon - mod or schematic for litematica

Minecraft launcher crashes when i try to run Minecraft Forge 1.13 - 1.19.2

Who's Online (See full list)

Important Information

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)

Chrome (Desktop)

Safari (iOS 16.4+)

Safari (macOS)

Edge (Android)

Edge (Desktop)

Firefox (Android)

Firefox (Desktop)