(Solved) Issue with forge (1.8) in Technic Launcher

[Famout]

A part of me is positive this will sound like a stupid question, but no harm in finding out!

 

I have a modpack I made for vanilla minecraft for use when playing on servers and such (minimap, health bars, inventory sort, etc) and of course due to being designed for "vanilla" it has the impossible trouble of trying to stay up to date.

 

Now forge 1.8 has been in beta for the longest time, but recently came out. I know people who where using the beta and managed to make it work for 1.8.1 with their vanilla client (although have encountered some bugs, but nothing breaking.)

 

With Forge coming officially out I have started trying to put it in my modpack, but have had no luck. These are the steps I take:

 

1. Get forge .jar universal (version 1299 currently)

2. Rename it into modpack.jar and put in "bin" folder.

3. Update version of modpack to force an update.

4. Crash

 

The log I get makes it sound as if it finds forge with little trouble, but fails to get any farther, here is the (thankfully short) log file. http://pastebin.com/ArJVSf07 When I launch the modded pack it just closes the launcher, then reopens swiftly as expected.

 

This is my largest problem of course, and I highly doubt it is caused by forge being 1.8 since I have heard of many others using it with little trouble, but I have also heard of stranger things causing conflicts. I also have tried putting forge in the mods folder, having it both in modpacks.jar and in the mods folder, and deleting the meta-inf file just in case, and none of which worked of course.

 

If anyone has advice I will gladly try it, and thanks in advance for your time!

 

P.S. If anyone also knows how to get optifine happy now with forge without needing to include the EULA breaking minecraft files please let me know! Hopefully it will be possible now in theory, although this is a much smaller problem.

[plowmanplow]

Forge for 1.8 does not include the libraries required to operate in the Launcher inside its version.json file. Those need to be added before it will work in a Technic custom modpack. You can either read up on the details and do it yourself:

 

 

Or you can use my BareBonesPack ( http://technicpack.net/modpack/barebonespack.271497 ) which has the Forge 1.8 versions pre-configured to work in the Launcher.

[Famout]

Sorry for the delay, but thanks for the reply, (You are everywhere on this forum too!)

Anyway, I tried entering in the code you provided and ended up with this in my "version.json" file: http://pastebin.com/aBvX2Ny7

Now it gets father then before, but still runs into issues: http://pastebin.com/98AJXggM

While it might be some kind of syntax error, I tried to compare it to the barebones pack and it mostly seems right, although I did notice in the barebonespack it seems like you put in more then just the directories you linked to in that forum (Might be misreading though.)

Thanks for helping a fool out like this!

[plowmanplow]

As of now Forge for 1.8 seems to function correctly in the Launcher when included directly with no modifications.

[Famout]

Thanks for the help, but I see to get the same exact error, here is just flat out putting forge universal (1.8-11.14.1.1338) into modpack.jar  http://pastebin.com/FJTbCbfL

[plowmanplow]

Always provide the API URL or a link to the pack details page when requesting custom modpack assistance.

[Famout]

Sorry, here it is. http://www.technicpack.net/modpack/map-nei-inventory-sort.433815/updates Despite the name nothing is inside of it right now other then trying to get Forge to work. I do not know how to set up multiple versions while using dropbox.

 

Edit: Also sounds like the forums need a bit of a hammering as well! Although glad to hear its bugs have been ironed out.

[plowmanplow]

• Your pack settings indicate that the MC version is 1.8.1. Forge is only for MC 1.8 and requires that you have 1.8 selected in your pack settings.

[Famout]

Ah, I was mislead. A friend is using 1.8 forge with 1.8.1 Minecraft, and the maker of forge even said he expected no differences between 1.8.1 Forge and 1.8 other then a name change so I assumed it would work.

After talking to my friend though I found out his forge minecraft though is running very buggy right now, so it only makes sense that adding another layer of complexity like the Technic launcher would make things even worse.

Still, that answers everything nicely, and unless you can somehow tell me when forge 1.8.1 is coming out, I think that takes care of everything! Thanks for the support.