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.
Please read the rules and FAQ before starting a new topic
Currently supported: All versions

1.12.2 Forge not showing up in launcher

tuffley42
in Support & Bug Reports

Featured Replies

Posted

Yesterday I tried to install forge 1.12.2 to use some mods, but when I opened up my launcher (I'm using the official Minecraft launcher) It wasn't showing up. I had installed a version of 1.14.3 forge previously, and it had shown up both automatically in the launcher and within the version drop down menu (1.12.2 wasn't showing up in either) I've tried both the installer and windows installer versions of 1.12.2 - 14.23.5.2768, 1.12.2 - 14.23.5.2838 and 1.12.2 - 14.23.0.2486 (all from the official forge website). The 1.12.2 forge versions are showing up within the versions folder, but each 1.12.2 forge version i have installed does not contain the executable jar file (which every other version (including 1.14.3 forge) contains) I have looked through other posts within this forum but none of them have been helpful (though I have seen a few people with similar issues). I also have the latest version of java installed, and I have played basic 1.12.2 previously. If you need anymore information please let me know, I will also attach screenshots to try to help. 

within 1.12.2 forge folder.PNG

Launcher.PNG

versions folder.PNG

Versions within launcher.PNG

For whatever reason 1.12.2 versions of Forge get sorted to the bottom of the list.

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]

 

    • Thanks 1
    • 2 weeks later...

    All you have to do is delete the 1.14 forge then redownlad the 1.12.2 forge it works

     

    I hope i helped

    Edited by trashTF2_F2P

    You do not need to delete other versions of Forge.

    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]

     

    • 1 month later...
    • 2 weeks later...

    I encountered this problem today with Forge versions 1.12.2 and 1.12.   Including a not so great workaround below for the community.

     

    Use Case: 

    As a parent I am attempting to install a mod (Tektopia) for my son and need to use Forge 1.12.2 as required by the Tektopia install guide.

    Minecraft Java Edition - Launcher 2.1.5964 is being used as the client 

     

    Problem  Description:  

    1. Downloaded Forge 1.12.2 and install per the installation guide (which really is just a copy of the standard installation instructions for the Forge client). 
    2. Install Forge 1.12.2 using the client option and making sure to verify that the installation path is correct.  Note that successful installation is indicated by the installer
    3. After installing the 1.12.2 Forge client I start the Minecraft Launcher . 
    4. I then look for Forge 1.12.2 listing in the Installations list so I can start the game using the desired mod
    • Note: The expected installation is not showing up at all in the launcher's list. 
    •  In opening launcher_profiles.json from my .minecraft folder I notice that there is an entry for the Forge 1.12.2 installation, however unlike the the other versions of Forge I have listed in the file, this version was given a tokenized name  for it's JSON "profiles" entry as opposed to "Forge" or "forge" as is used by my other profiles.  I referenced 2 other systems I own with Minecraft mods installed and noticed all of the other profile names are either "Forge" or "forge".  These are the defaults given by the Forge installer and not touched by me.

    Workaround:

    This is not a great workaround and is destructive, but should provide a clue to a knowledgeable developer or Minecraft enthusiast as to what the root cause is.  This is as far as I was willing to take my investigations.

     

    Warning: the following "workaround" will essentially cause Minecraft to write a new version of the file which will remove all previous profile listings and require you to login again with valid credentials.  

     

    1. Either 'touch' launcher_profiles.json by making saving it or delete the file altogether.   If you touch the file by making a minor edit, Minecraft will wipe the file and write a new one without your previous profiles. 
    2. Start the Minecraft launcher.  You will be prompted for your login credentials
    3. Once the launcher has started the 1.12.2 (or 1.12) forge profile will be in the list of installation profiles.  In looking at launcher_profiles.json the profile name will now appear as "forge" instead of the tokenized name that was noticed when the 1.12.2 installer was used.
    • 3 months later...

    I had the same issue. What helped for me was that I had a different minecraft tab open. After I had closed it I installed it again and it showed up.

    Guest
    This topic is now closed to further replies.
    https://forums.minecraftforge.net/topic/72891-1122-forge-not-showing-up-in-launcher/
    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.