Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

unable to install Forge on MC 1.5.2


Recommended Posts

I wanted to play old CTM maps made by Vechs.

so I downloaded Forge(forge-1.5.2-7.8.1.738-installer.jar) for 1.5.2 and tried to install and got this error

image.png.868d53f56ee955dc1d6a387304a213b5.png

 

Since original minecraft launcher did not work I deleted everthing and went ahead tried ForgeOptiFine 1.5.2 from TLauncher to see if it was only original minecraft issue.

but this is what I got from TLauncher as well.

image.png.36c7bff26c37b354fc2921856f2ad51e.png

here is the log:

Spoiler

2021-04-30 18:25:14 [INFO] [ForgeModLoader] Forge Mod Loader version 5.2.23.738 for Minecraft 1.5.2 loading
2021-04-30 18:25:14 [INFO] [ForgeModLoader] Java is Java HotSpot(TM) 64-Bit Server VM, version 1.8.0_51, running on Windows 8.1:amd64:6.3, installed at C:\Program Files\Java\jre1.8.0_51
2021-04-30 18:25:14 [FINE] [ForgeModLoader] Java classpath at launch is C:\Users\MasterRace\AppData\Roaming\.minecraft\libraries\optifine\OptiFine\1.5.2_HD_U_D5\OptiFine-1.5.2_HD_U_D5.jar;C:\Users\MasterRace\AppData\Roaming\.minecraft\libraries\net\minecraftforge\minecraftforge\1.5.2-7.8.1.738\minecraftforge-1.5.2-7.8.1.738.jar;C:\Users\MasterRace\AppData\Roaming\.minecraft\libraries\org\scala-lang\scala-library\2.10.0-custom\scala-library-2.10.0-custom.jar;C:\Users\MasterRace\AppData\Roaming\.minecraft\libraries\net\sourceforge\argo\argo\3.2-small\argo-3.2-small.jar;C:\Users\MasterRace\AppData\Roaming\.minecraft\libraries\org\bouncycastle\bcprov-jdk15on\1.48\bcprov-jdk15on-1.48.jar;C:\Users\MasterRace\AppData\Roaming\.minecraft\libraries\com\google\guava\guava\14.0-rc3\guava-14.0-rc3.jar;C:\Users\MasterRace\AppData\Roaming\.minecraft\libraries\net\minecraftforge_temp\legacy\legacyfixer\1.0\legacyfixer-1.0.jar;C:\Users\MasterRace\AppData\Roaming\.minecraft\libraries\net\minecraft\launchwrapper\1.5\launchwrapper-1.5.jar;C:\Users\MasterRace\AppData\Roaming\.minecraft\libraries\net\sf\jopt-simple\jopt-simple\4.5\jopt-simple-4.5.jar;C:\Users\MasterRace\AppData\Roaming\.minecraft\libraries\org\ow2\asm\asm-all\4.1\asm-all-4.1.jar;C:\Users\MasterRace\AppData\Roaming\.minecraft\libraries\net\java\jinput\jinput\2.0.5\jinput-2.0.5.jar;C:\Users\MasterRace\AppData\Roaming\.minecraft\libraries\net\java\jutils\jutils\1.0.0\jutils-1.0.0.jar;C:\Users\MasterRace\AppData\Roaming\.minecraft\libraries\org\lwjgl\lwjgl\lwjgl\2.9.0\lwjgl-2.9.0.jar;C:\Users\MasterRace\AppData\Roaming\.minecraft\libraries\org\lwjgl\lwjgl\lwjgl_util\2.9.0\lwjgl_util-2.9.0.jar;C:\Users\MasterRace\AppData\Roaming\.minecraft\versions\ForgeOptiFine 1.5.2\ForgeOptiFine 1.5.2.jar
2021-04-30 18:25:14 [FINE] [ForgeModLoader] Java library path at launch is C:\Users\MasterRace\AppData\Roaming\.minecraft\versions\ForgeOptiFine 1.5.2\natives
2021-04-30 18:25:14 [FINE] [ForgeModLoader] Enabling runtime deobfuscation
2021-04-30 18:25:14 [FINEST] [ForgeModLoader] All core mods are successfully located
2021-04-30 18:25:14 [INFO] [ForgeModLoader] Found a command line coremod : net.minecraftforge.legacy._1_5_2.LibraryFixerCoremod
2021-04-30 18:25:14 [INFO] [ForgeModLoader] [LegacyFixer] Removing CoreFMLLibraries: cpw.mods.fml.relauncher.CoreFMLLibraries@7b69c6ba
2021-04-30 18:25:14 [FINEST] [ForgeModLoader] Discovering coremods
2021-04-30 18:25:14 [FINEST] [ForgeModLoader] Downloading file http://files.minecraftforge.net/fmllibs/deobfuscation_data_1.5.2.zip
2021-04-30 18:25:14 [INFO] [ForgeModLoader] Downloading file http://files.minecraftforge.net/fmllibs/deobfuscation_data_1.5.2.zip
2021-04-30 18:25:14 [SEVERE] [ForgeModLoader] There were errors during initial FML setup. Some files failed to download or were otherwise corrupted. You will need to manually obtain the following files from these download links and ensure your lib directory is clean.
2021-04-30 18:25:14 [SEVERE] [ForgeModLoader] *** Download http://files.minecraftforge.net/fmllibs/deobfuscation_data_1.5.2.zip
2021-04-30 18:25:14 [SEVERE] [ForgeModLoader] <===========>
2021-04-30 18:25:14 [SEVERE] [ForgeModLoader] The following is the errors that caused the setup to fail. They may help you diagnose and resolve the issue
2021-04-30 18:25:14 [SEVERE] [ForgeModLoader] The downloaded file deobfuscation_data_1.5.2.zip has an invalid checksum e04c5335922c5e457f0a7cd62c93c4a7f699f829 (expecting 446e55cd986582c70fcf12cb27bc00114c5adfd9). The download did not succeed correctly and the file has been deleted. Please try launching again.
2021-04-30 18:25:14 [SEVERE] [ForgeModLoader] <<< ==== >>>
2021-04-30 18:25:14 [SEVERE] [ForgeModLoader] The following is diagnostic information for developers to review.
2021-04-30 18:25:14 [SEVERE] [ForgeModLoader] Error details
java.lang.RuntimeException: The downloaded file deobfuscation_data_1.5.2.zip has an invalid checksum e04c5335922c5e457f0a7cd62c93c4a7f699f829 (expecting 446e55cd986582c70fcf12cb27bc00114c5adfd9). The download did not succeed correctly and the file has been deleted. Please try launching again.
    at cpw.mods.fml.relauncher.RelaunchLibraryManager.performDownload(RelaunchLibraryManager.java:613)
    at cpw.mods.fml.relauncher.RelaunchLibraryManager.downloadFile(RelaunchLibraryManager.java:532)
    at cpw.mods.fml.relauncher.RelaunchLibraryManager.handleLaunch(RelaunchLibraryManager.java:165)
    at cpw.mods.fml.relauncher.FMLRelauncher.setupHome(FMLRelauncher.java:172)
    at cpw.mods.fml.relauncher.FMLRelauncher.relaunchClient(FMLRelauncher.java:104)
    at cpw.mods.fml.relauncher.FMLRelauncher.handleClientRelaunch(FMLRelauncher.java:38)
    at net.minecraft.client.Minecraft.main(Minecraft.java:2237)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at net.minecraft.launchwrapper.Launch.launch(Launch.java:57)
    at net.minecraft.launchwrapper.Launch.main(Launch.java:18)

 

I am guessing that Forge cannot download certain file from the server by reading this ->

Quote

2021-04-30 18:25:14 [SEVERE] [ForgeModLoader] The following is the errors that caused the setup to fail. They may help you diagnose and resolve the issue
2021-04-30 18:25:14 [SEVERE] [ForgeModLoader] The downloaded file deobfuscation_data_1.5.2.zip has an invalid checksum e04c5335922c5e457f0a7cd62c93c4a7f699f829 (expecting 446e55cd986582c70fcf12cb27bc00114c5adfd9). The download did not succeed correctly and the file has been deleted. Please try launching again.

 

Any ways to fix the issue? really want to experience Vech's map again :'(

 

Edited by noopii
to emphatise
Link to post
Share on other sites

Are you really going after 1.5.2 or are you trying to go for 1.15.2 and forgetting a 1?

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]

 

Link to post
Share on other sites
Posted (edited)
15 minutes ago, DaemonUmbra said:

Are you really going after 1.5.2 or are you trying to go for 1.15.2 and forgetting a 1?

1.5.2 is right

which came out 7 years ago

had so much memories playing it haha(esp. CTM maps)

 

I kinda concluded that it is a Forge's server side issue since I was not able to install on other computer as well.(getting same error msg)

Am here just wondering if there is any other alternative way to install Forge on 1.5.2 MC(archive for deobfuscation_data_1.5.2.zip etc etc)

Edited by noopii
Link to post
Share on other sites

Really old Minecraft versions are 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.

 

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]

 

Link to post
Share on other sites
Guest
This topic is now closed to further replies.


×
×
  • Create New...

Important Information

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