Forge library locations?

[Braxbro]

My computer doesn't allow the installer to run (no admin) and so I am installing manually. However, on both 1.7.10 and 1.10.2 versions of Forge, 13 libraries are missing from the universal copy of the install. Where can I find these?

[Braxbro]

17 minutes ago, diesieben07 said:

• The installer does not need admin permissions.
• Use the installer.

Regardless, I get errors from Java when I try to run an installer because it's accessing out of bounds areas. The installers won't work. I need the libraries.

[Braxbro]

Just now, diesieben07 said:

The installer works fine, if it doesn't that's a bug. Please post the installer log resp. the error message you get.

1.7 installer needs admin. 

[Braxbro]

Log files:

forge-1.10.2-12.18.3.2185-installer.jar.log

forge-1.7.10-10.13.4.1614-1.7.10-installer.jar.log

[Braxbro]

1 minute ago, diesieben07 said:

Stop using 1.7.10.

You kidding? All the best modpacks are for 1.7.10! I use the 1.10 packs too but I enjoy the 1.7 ones as well.

[Braxbro]

1 minute ago, diesieben07 said:

Great. 1.7.10 is 3 1/2 years old. It is no longer maintained by Forge. If it works for you, great.

But in a case like this, someone would have to go back and fix the old installers, I doubt anyone is going to do that.

I have the Universal copy, it's just asking for 13 specific library files. I can compile a list for you if you like. (Edit: The Forge profile has been created, it just errors when I try to open it)

Edited November 15, 2017 by Braxbro
Correction

[Braxbro]

Just now, diesieben07 said:

These libraries are installed by the installer.

Yes... I realize that. They'd also be installed by the launcher if I wasn't offline rn and using cell data to do this. The profile is all set up (and heck, the issue is that the libraries aren't packaged in with the installer lol, if someone went and got them and took the installer, they could add the libraries and recompile and it'd work fine lol)

[Braxbro]

4 minutes ago, diesieben07 said:

No. The installer exists for a reason. If the launcher was able to do this, there would not be an installer.

 

Doubtful, unless you created the version JSON files necessary for the launcher to understand how to launch by hand. This is also done by the installer.

 

This is intentional. If you install 10 different versions of Forge that share the same library the library is downloaded once. If it were packaged with the installer, it'd have to be downloaded 10 times.

 

You don't understand how this works, do you?

I understand how it works. If the libraries were packaged with the installer, then it'd work. I understand the issue with the ten installs and ten resulting copies of the libraries. The launcher can do it, and the version.json file is inside the .jar on the universal install.

Edited November 15, 2017 by Braxbro
Corrected myself

[Braxbro]

5 minutes ago, diesieben07 said:

No, the launcher cannot download the Forge specific libraries.

 

Not sure why it's there, it certainly doesn't belong there and it is not of any use there.

It's in every universal install.

[Braxbro]

2 minutes ago, diesieben07 said:

I know. It's probably an overlooked artifact of the build process. Only the installer needs it.

Or, you know, it's for jar incompatible systems that can run Minecraft.

[Braxbro]

Just now, diesieben07 said:

I don't know what you mean by "jar incompatible system". The most logical explanation I can come up with is "a system that cannot run Java", which is by definition a system which cannot run Minecraft (the PC edition anyways).

It could be that the version.json is inside of the universal install so that devices that can't run the .jar installers or the windows installers can install Forge. And yes, MC runs without java installed now. The new native launcher allows that.

[Braxbro]

2 minutes ago, diesieben07 said:

In that case it makes more sense to get it from the installer jar. It has no business in the universal jar.

 

The native launcher has a bundled Java. Minecraft needs Java, period.

Good point. I don't understand why Forge has the versions.json in the universal install either, just guessing at possible reasons.

 

 

[LexManos]

Jesus christ you two, quit bickering.

The universal has the version.json in it for anyone who knows what they are doing and give a shit about it to use. That's it. Its there because there is no reason for it NOT to be there.

As for the installer bundling the libraries. This will never happen. Simply put it would multiply the storage costs on our servers 40 fold with redundant data. Hence the point of having the installer download the files.

 

As for the issue you are having with being able to use the installer. You need a internet connection, thats the rub of it. Something in your setup is screwing with the list of mirrors the installer downloads. Check your firewall/proxy/whatever settings. I just verified with that installer that it works fine with a valid internet connection. So the installer is fine.

 

As for 1.7.10, Diesbien is correct. You should stop using it if you expect support here on the forums. It's 3+ years old I don't care if you play it but its ancient in Minecraft terms and expecting us to actively support you using it is just plain wrong.

Now, as for the libraries itself. We do have this archive that contains some of the libraries. I have not verified that it contains everything needed for 1.7.10, because again it's old as hell and we don't actively provide support for it. Maybe if Diesieben or someone else wants to gather up a list of libraries for 1.7.10 I can add them in.

 

Anyways, No Forge installer need admin access. It only write to the folder you tell it to. By default that being the %appdata%/.minecraft folder. Which DOES NOT require admin privileges, which is why Minecraft uses that folder. As I said above, the issue is your network settings. Something is in the middle corrupting the data being downloaded by the installer.

[Braxbro]

1 hour ago, LexManos said:

Jesus christ you two, quit bickering.

The universal has the version.json in it for anyone who knows what they are doing and give a shit about it to use. That's it. Its there because there is no reason for it NOT to be there.

As for the installer bundling the libraries. This will never happen. Simply put it would multiply the storage costs on our servers 40 fold with redundant data. Hence the point of having the installer download the files.

 

As for the issue you are having with being able to use the installer. You need a internet connection, thats the rub of it. Something in your setup is screwing with the list of mirrors the installer downloads. Check your firewall/proxy/whatever settings. I just verified with that installer that it works fine with a valid internet connection. So the installer is fine.

 

As for 1.7.10, Diesbien is correct. You should stop using it if you expect support here on the forums. It's 3+ years old I don't care if you play it but its ancient in Minecraft terms and expecting us to actively support you using it is just plain wrong.

Now, as for the libraries itself. We do have this archive that contains some of the libraries. I have not verified that it contains everything needed for 1.7.10, because again it's old as hell and we don't actively provide support for it. Maybe if Diesieben or someone else wants to gather up a list of libraries for 1.7.10 I can add them in.

 

Anyways, No Forge installer need admin access. It only write to the folder you tell it to. By default that being the %appdata%/.minecraft folder. Which DOES NOT require admin privileges, which is why Minecraft uses that folder. As I said above, the issue is your network settings. Something is in the middle corrupting the data being downloaded by the installer.

Yep, that's basically the case. My firewall, which I don't have admin access over, doesn't play nice with .jars and .exes not on a whitelist. Forge can't access the Internet - it's effectively offline.

 

as for a list, I can have that for you tomorrow.

 

Wait lex...

 

Have you thought of a libraries download each version? The libraries aren’t too big, and so if you only stored one copy of a library list in a .zip for every time you upgrade versions of stuff (so like 1.7.10 to 1.10.2 (I think)). That way, if you need the libraries as one concise download, you can get them, but if you don't, it doesn't take up as much space as bundling with the launcher. Heck, even just a 'libraries' dropdown for each Forge version allowing you to download each library individually via link.

Edited November 16, 2017 by Braxbro
Edited to add a sentence