Sulhythal Posted October 28, 2013 Posted October 28, 2013 I just want to repeat my thanks for this guide! I went through with a refresher when I updated my server to 1.6 recently, just to make sure I was doing everything right.
TheScout96 Posted October 30, 2013 Posted October 30, 2013 I followed the steps but when it came to the part where you need to extract forge to the bin folder, then compress it, naming it modpack.jar and compressing the files, it's a WinRAR archive file, I changed the file extensions but still doesn't show up as .zip or .jar Help please?
SXScarecrow Posted October 31, 2013 Posted October 31, 2013 I'm far too nice. Download links for relevant versions of the modpack.jar below. 1.4.7 1.5.2 1.6.2 1.6.4
TheScout96 Posted November 1, 2013 Posted November 1, 2013 Oh my goodness, thanks Scare! Your "Far to nice" -ness is VERY appreciated!
lukeb28 Posted November 1, 2013 Author Posted November 1, 2013 I'm far too nice. Download links for relevant versions of the modpack.jar below. 1.4.7 1.5.2 1.6.2 1.6.4 I'll put those in the OP.
SXScarecrow Posted November 1, 2013 Posted November 1, 2013 Cheers luke, I was going to suggest it anyway! I'll update for new versions of Minecraft as required.
Tehkiah Posted November 2, 2013 Posted November 2, 2013 The section for LiteLoader doesn't seem relevant, at least not when using Forge on version 1.6.4. If you install forge and then add the liteloader files extracted from the installer it crashes the launcher before the game can even start up :(
SXScarecrow Posted November 2, 2013 Posted November 2, 2013 I am re-writing the section on Liteloader since I wrote it in the first place; as long as luke makes it clear in the OP that the previous instructions were for 1.5.2 and lower.
Tehkiah Posted November 2, 2013 Posted November 2, 2013 I am re-writing the section on Liteloader since I wrote it in the first place; as long as luke makes it clear in the OP that the previous instructions were for 1.5.2 and lower. Gotcha, after messing around with it for a while, I assumed it was probably accurate for 1.5.2. So wait does this mean there's a way to get it working for 1.6.4 with Forge and the Technic Launcher Platform? I cannot figure it out for the life of me.
SXScarecrow Posted November 2, 2013 Posted November 2, 2013 There probably is; if I remember correctly I had to smash Liteloader into my files for 1.5.2 as well. I think its because the new way the Technic Launcher handles files that causes the issues. I'm working on it
Tehkiah Posted November 2, 2013 Posted November 2, 2013 There probably is; if I remember correctly I had to smash Liteloader into my files for 1.5.2 as well. I think its because the new way the Technic Launcher handles files that causes the issues. I'm working on it Oh excellent! So glad someone who knows better is looking into it haha I'm really hoping it's doable since the Platform is so damned useful and liteloader is so indispensable for my modpack!
SXScarecrow Posted November 2, 2013 Posted November 2, 2013 Since the Platform is so damned useful and liteloader is so indispensable for my modpack! I also love a few litemods thrown in....everything becomes so much prettier with them Although, some Voxel mods now support Forge, so there's an idea.
Tehkiah Posted November 3, 2013 Posted November 3, 2013 I also love a few litemods thrown in....everything becomes so much prettier with them Although, some Voxel mods now support Forge, so there's an idea. Yeah Voxel mods are nice but I'm mostly trying to use Liteloader for the Macro Keybind mod for my server, it's ridiculously important and there's absolutely no other mod that does what it does apparently. It's very frustrating to be unable to use it with this launcher, since it kills a lot of important features for me. It really bums me out that the liteloader author changed how it installs for some reason.
Tehkiah Posted November 6, 2013 Posted November 6, 2013 Anyone come up with any solutions for this liteloader thing?
Tehkiah Posted November 6, 2013 Posted November 6, 2013 So I tried the manual installation option listed in the Liteloader thread. It involves adding some classes to the version.json file to get the launcher to download what it needs to get liteloader working. Unfortunately, it seems like the Technic launcher likes to download or overwrite this file instead of using whatever one is included in the bin folder. Not really sure what else to do here, this is driving me bananas. Edit: seems like the version file has to be in the version folder but Technic doesn't utilize this so....uhhhh...ANNOYING.
Sam Redman Posted November 18, 2013 Posted November 18, 2013 Yeah I'm having the same issue. In order to install liteloader, the version.json needs to be edited. Problem is the launcher overwrites any edited version.json files that are included in the modpack. :/
SXScarecrow Posted November 18, 2013 Posted November 18, 2013 Try putting the version.json inside the modpack.jar. According to CanVox, the launcher attempts to extract the version.json from inside the modpack.jar. If it fails, then it overwrites the version.json. I'm not 100% sure it will work, but try anyway.
Sam Redman Posted November 19, 2013 Posted November 19, 2013 Try putting the version.json inside the modpack.jar. According to CanVox, the launcher attempts to extract the version.json from inside the modpack.jar. If it fails, then it overwrites the version.json. I'm not 100% sure it will work, but try anyway. Ah! Perfect, that seems to work. Thank you very much for your help :)
Tehkiah Posted November 19, 2013 Posted November 19, 2013 Try putting the version.json inside the modpack.jar. According to CanVox, the launcher attempts to extract the version.json from inside the modpack.jar. If it fails, then it overwrites the version.json. I'm not 100% sure it will work, but try anyway. I hadn't even thought to check the Forge files for a version.json that would be overwriting! That's brilliant! I, too, can confirm that this method works! Thanks a bunch Scarecrow!
nyxar3212 Posted November 22, 2013 Posted November 22, 2013 when i try to install mekanism from voltz, "Forge Mod Loader has found a problem with your minectaft installation The mods and versions listed below could not be found numina : any The file 'ForgeModLoader-client-0.log' contains more information" Help? tell me how to add a spoiler and i will post the log
Chefsbrian Posted November 22, 2013 Posted November 22, 2013 Put the log onto pastebin and fire the link off here. You usually see that sort of issue for mismatching versions of things, such as using an older version of forge than a mod will support, or putting a newer mod into an older version, ect.
MarioPower Posted November 27, 2013 Posted November 27, 2013 Doesn't work for me, like everything else on this cum-puter. I F*cking hate it. At this time, I have like 14 modpack folders in my resycle bin that I attempted to make.
FiberSprite Posted November 29, 2013 Posted November 29, 2013 Okay so i am getting a error where it cant open the zip properly even though it downloads it . please help me .
lukeb28 Posted December 3, 2013 Author Posted December 3, 2013 How about 1.6? As far as I can tell from the last Modpack I made, the only thing that has changed is the lack of need for a coremods folder. Everything else is still the same. Doesn't work for me, like everything else on this cum-puter. I F*cking hate it. At this time, I have like 14 modpack folders in my resycle bin that I attempted to make. The relevance of your post eludes me, please describe better what your problem is. Okay so i am getting a error where it cant open the zip properly even though it downloads it . please help me .You may have saved the file as a .rar in stead of a .zip. make sure you have the compression set correctly or it will not work.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now