I need help with installing Forge 1.12.2

Posted July 15, 20196 yr

So for what I've been seeing that could be the problem is in the logs which is this:

java.net.preferIPv4Stack=true
Considering library net.minecraftforge:forge:1.12.2-14.23.5.2768: Not Downloading {Wrong Side}
Considering library net.minecraft:launchwrapper:1.12: Not Downloading {Wrong Side}
Considering library org.ow2.asm:asm-all:5.2
Considering library org.jline:jline:3.5.1: Not Downloading {Wrong Side}
Considering library net.java.dev.jna:jna:4.4.0: Not Downloading {Wrong Side}
Considering library com.typesafe.akka:akka-actor_2.11:2.3.3
Checking "C:\Users\drago\AppData\Roaming\.minecraft\libraries\com\typesafe\akka\akka-actor_2.11\2.3.3\akka-actor_2.11-2.3.3.jar" internal checksums
checksums.sha1 validated successfully
Jar contents validated successfully
Considering library com.typesafe:config:1.2.1
Checking "C:\Users\drago\AppData\Roaming\.minecraft\libraries\com\typesafe\config\1.2.1\config-1.2.1.jar" internal checksums
checksums.sha1 validated successfully
Jar contents validated successfully
Considering library org.scala-lang:scala-actors-migration_2.11:1.1.0
Checking "C:\Users\drago\AppData\Roaming\.minecraft\libraries\org\scala-lang\scala-actors-migration_2.11\1.1.0\scala-actors-migration_2.11-1.1.0.jar" internal checksums
checksums.sha1 validated successfully
Jar contents validated successfully
Considering library org.scala-lang:scala-compiler:2.11.1
Checking "C:\Users\drago\AppData\Roaming\.minecraft\libraries\org\scala-lang\scala-compiler\2.11.1\scala-compiler-2.11.1.jar" internal checksums
checksums.sha1 validated successfully
Jar contents validated successfully
Considering library org.scala-lang.plugins:scala-continuations-library_2.11:1.0.2
Checking "C:\Users\drago\AppData\Roaming\.minecraft\libraries\org\scala-lang\plugins\scala-continuations-library_2.11\1.0.2\scala-continuations-library_2.11-1.0.2.jar" internal checksums
checksums.sha1 validated successfully
Jar contents validated successfully
Considering library org.scala-lang.plugins:scala-continuations-plugin_2.11.1:1.0.2
Checking "C:\Users\drago\AppData\Roaming\.minecraft\libraries\org\scala-lang\plugins\scala-continuations-plugin_2.11.1\1.0.2\scala-continuations-plugin_2.11.1-1.0.2.jar" internal checksums
checksums.sha1 validated successfully
Jar contents validated successfully
Considering library org.scala-lang:scala-library:2.11.1
Checking "C:\Users\drago\AppData\Roaming\.minecraft\libraries\org\scala-lang\scala-library\2.11.1\scala-library-2.11.1.jar" internal checksums
checksums.sha1 validated successfully
Jar contents validated successfully
Considering library org.scala-lang:scala-parser-combinators_2.11:1.0.1
Checking "C:\Users\drago\AppData\Roaming\.minecraft\libraries\org\scala-lang\scala-parser-combinators_2.11\1.0.1\scala-parser-combinators_2.11-1.0.1.jar" internal checksums
checksums.sha1 validated successfully
Jar contents validated successfully
Considering library org.scala-lang:scala-reflect:2.11.1
Checking "C:\Users\drago\AppData\Roaming\.minecraft\libraries\org\scala-lang\scala-reflect\2.11.1\scala-reflect-2.11.1.jar" internal checksums
checksums.sha1 validated successfully
Jar contents validated successfully
Considering library org.scala-lang:scala-swing_2.11:1.0.1
Checking "C:\Users\drago\AppData\Roaming\.minecraft\libraries\org\scala-lang\scala-swing_2.11\1.0.1\scala-swing_2.11-1.0.1.jar" internal checksums
checksums.sha1 validated successfully
Jar contents validated successfully
Considering library org.scala-lang:scala-xml_2.11:1.0.2
Checking "C:\Users\drago\AppData\Roaming\.minecraft\libraries\org\scala-lang\scala-xml_2.11\1.0.2\scala-xml_2.11-1.0.2.jar" internal checksums
checksums.sha1 validated successfully
Jar contents validated successfully
Considering library lzma:lzma:0.0.1: Not Downloading {Wrong Side}
Considering library net.sf.jopt-simple:jopt-simple:5.0.3: Not Downloading {Wrong Side}
Considering library java3d:vecmath:1.5.2
Considering library net.sf.trove4j:trove4j:3.0.3
Considering library org.apache.maven:maven-artifact:3.5.3
Extracting: /forge-1.12.2-14.23.5.2768-universal.jar
To: C:\Users\drago\AppData\Roaming\.minecraft\libraries\net\minecraftforge\forge\1.12.2-14.23.5.2768\forge-1.12.2-14.23.5.2768.jar

TL;DR- I got a ton of "Wrong Side" stuff in the logs?

July 15, 20196 yr

What is the actual error when you try to run 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]

July 15, 20196 yr

Author

Just now, DaemonUmbra said:

What is the actual error when you try to run the game?

Well there is no error, after I open the forge installer and click install client/ok it says that its been successfully installed but wont show up in the launcher. it will show up in the Versions folder but it adds one folder the json file and when i open minecraft the v1.12.2 version it will add another folder by the same name/different number of the forge folder and it will have the resource packs, saves, and logs in it

Edited July 15, 20196 yr by Captain Thárros

July 15, 20196 yr

Author

Well I suppose that would be the error since it isnt doin what its supposed to do

July 15, 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 15, 20196 yr

Author

This is the minecraft launcher if that's what you mean, but if not the installer I'm using is "forge-1.12.2-14.23.5.2768-installer"

July 16, 20196 yr

Forge installs itself as a version of Minecraft, make a new Profile/Installation and select Forge as the version (1.12.2 versions of Forge get booted to the bottom of the list for whatever reason)

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 16, 20196 yr

Author

4 hours ago, DaemonUmbra said:

Forge installs itself as a version of Minecraft, make a new Profile/Installation and select Forge as the version (1.12.2 versions of Forge get booted to the bottom of the list for whatever reason)

ohhhh ok, thank you! I really appreciate it, sorry for the late reply. I'll try that now

Edit: I tried it and it wooooorked! You're the best! ❤️

Edited July 16, 20196 yr by Captain Thárros

April 13, 20205 yr

now into 2020, and i have the same problem. This time i downloaded the forge windows installer, and i did what you said above. however its still not working for me

April 13, 20205 yr

Please don't necro old threads. If you have an issue please make your own thread.

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

I need help with installing Forge 1.12.2

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)