Jump to content

Recommended Posts

Posted

I have the same problem. I think I've come to the conclusion that this new launcher version isn't working properly with custom modpacks. They had to release a new version as quick as possible this morning because of a minecraft changing one of their directories. I think they fixed that problem, but something else got bugged in the process. A lot of other people have recently run into this problem so this would be the most logical conclusion. I don't think anyone on here will know the answer. All we can do is wait for Technic to fix the problem. Let's just hope they get it fixed soon.

Posted

I'm having this issue as well. I don't think I can test the pack I'm building until this is fixed... shoot.

Who's bright idea was it to use such a lousy error code, anyway? it's not particularly actionable. It took me over an hour to find this thread because I spent time finding out that this solution and that solution didn't work.

I might be able to use the slightly outdated copy of the launcher I have on my server computer... hmm...

wish me luck.

yup the outdated copy of the launcher worked. Someone send me a message when they push an update that fixes this.

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...