Jump to content

Forge Mod Loader (client) 1.5.2 Does not work anymore due to mojang file changes


Recommended Posts

Posted

This is a post I wrote in a different forum, but then thought to come here: it is kind of poorly written since it is 4am right now and im frustrated and tired of searching for a fix for this problem. If what I have wrote does not make sense. please ask me to clarify!

 

Anyways:

 

The new minecraft client does not create a bin folder anymore, they now have everything in .minecraft/versions. I am confused now because every tutorial on how to install FML with 1.5.2 says you have to go to bin folder and do some stuff to the .jar file. So now with the new location, I do that there and it does not work the same as how mojang used to have the files set up. I do no think it is possible atm to use the original 1.5.2 mod loader anymore. I think it needs to have a actual fml installer for 1.5.2 like it does for 1.6.2.

 

If someone can download a brand new fresh copy, and try get fml working for 1.5.2 and tell me how. This would make my day so much. Everyone that asked about no bin folder, they either say, re download it. but they don't install the files the same anymore. so that wont fix. and nobody has put up a solution yet..

 

 

After Thought:

Since the 1.6.2 Update, the file construction for the .minecraft folder is different and most likely all other fml version do no work. Would it be possible to make an installer version like 1.6.2 fml which is so much more user friendly and quick to use.

 

Thanks for reading, I really hope this post is in the right place, if it is not, please let me know so I can move it!

 

-Razors

Posted

There are instructions out there on how to copy the version folder and edit the jar. Think of the version folder as the old bin folder with some extra stff. After I get home I was gunna take a look into making a 1.5.2 installer but remember we don't officially support older versions

 

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • When I first heard about Bitcoin back in 2018, I was skeptical. The idea of a decentralized, digital currency seemed too good to be true. But I was intrigued as I learned more about the technology behind it and its potential. I started small, investing just a few hundred dollars, dipping my toes into the cryptocurrency waters. At first, it was exhilarating to watch the value of my investment grow exponentially. I felt like I was part of the future, an early adopter of this revolutionary new asset. But that euphoria was short-lived. One day, I logged into my digital wallet only to find it empty - my Bitcoin had vanished without a trace. It turned out that the online exchange I had trusted had been hacked, and my funds were stolen. I was devastated, both financially and emotionally. All the potential I had seen in Bitcoin was tainted by the harsh reality that with decentralization came a lack of regulation and oversight. My hard-earned money was gone, lost to the ether of the digital world. This experience taught me a painful lesson about the price of trust in the uncharted territory of cryptocurrency. While the technology holds incredible promise, the risks can be catastrophic if you don't approach it with extreme caution. My Bitcoin investment gamble had failed, and I was left to pick up the pieces, wiser but poorer for having placed my faith in the wrong hands. My sincere appreciation goes to MUYERN TRUST HACKER. You are my hero in recovering my lost funds. Send a direct m a i l ( muyerntrusted ( @ ) mail-me ( . )c o m ) or message on whats app : + 1 ( 4-4-0 ) ( 3 -3 -5 ) ( 0-2-0-5 )
    • You could try posting a log (if there is no log at all, it may be the launcher you are using, the FAQ may have info on how to enable the log) as described in the FAQ, however this will probably need to be reported to/remedied by the mod author.
    • So me and a couple of friends are playing with a shitpost mod pack and one of the mods in the pack is corail tombstone and for some reason there is a problem with it, where on death to fire the player will get kicked out of the server and the tombstone will not spawn basically deleting an entire inventory, it doesn't matter what type of fire it is, whether it's from vanilla fire/lava, or from modded fire like ice&fire/lycanites and it's common enough to where everyone on the server has experienced at least once or twice and it doesn't give any crash log. a solution to this would be much appreciated thank you!
    • It is 1.12.2 - I have no idea if there is a 1.12 pack
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.