Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cache for Minecraft Launcher (clarification?) #78

Closed
some-username-here1 opened this issue Feb 18, 2019 · 1 comment
Closed

Cache for Minecraft Launcher (clarification?) #78

some-username-here1 opened this issue Feb 18, 2019 · 1 comment
Labels

Comments

@some-username-here1
Copy link
Contributor

Since the new launcher forces https when it comes to downloading within the launcher, as I've tested a couple of times (before PR #72 was reverted), being this one (as a exe instead of a jar file):
Minecraft Launcher v2.1.2468

The solution for getting the cache to work is using the old (legacy?) version of the launcher, being this one (as it doesn't force https, I think):
Minecraft Launcher v1.6.84-j

@VibroAxe
Copy link
Member

Hi @some-username-here1
We've given this some though and given the relatively small file size of minecraft downloads and the likely hood of people running the newer launch I don't think it's sensible to add the minecraft domains back in. From experience they are more likely to create confusion with the cache "not working" than the benefit gained for a few network users still using the old launcher (which I don't believe is officially supported anymore anyway)

We are working on the ability to switch the dns image to use your own repo which would enable you to add your own domains to the list without us, but thats not quite finished yet. Watch lancachenet/lancache-dns#68 for details

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants