Closed SoxxZ closed 8 years ago
First of all, there is strong evidence that the MMC you use does not come from multimc.org, but it more likely is a cracked version. Start by using the offical client from https://multimc.org . We can not help you when you're using a modified version of MMC, as we have no clue what was changed / edited.
Also, I edited your comment to put the MC log in code tags; but for the future please just use the "Upload Log" button and just give us the link.
It might be an an issue with that particular forge version, but it looks like he (whoever he is) uses a Version changed by a third party. He should use the official version downloaded from https://MultiMC.org, we don't provide support for custom builds (isn't it a license violation to change MultiMC and distribute the changed version without changing the name to no longer include to word MultiMC?)
Practically, you added all mods as jar mods. That sometimes works, but most likely is the cause of the problem here.
Why do you need this 'cracked' version? And what would you need for it to be unnecessary?
well , I'm from Brazil , and I just change my home, and I'm no internet on my computer , so I'm unable to log me in MultiMC , so I'm using this , to edit my modpack for now I have no internet at home.
Well, the offline mode should still work. It's there for that exact reason. You just need an account that was at some point active. Or you can fake it.
Example accounts.json
:
{
"accounts": [
{
"accessToken": "00deadbeef00deadbeef00deadbeef00",
"activeProfile": "00deadbeef00deadbeef00deadbeef00",
"clientToken": "00deadbeef00deadbeef00deadbeef00",
"profiles": [
{
"id": "00deadbeef00deadbeef00deadbeef00",
"legacy": false,
"name": "whatever-nick-you-want"
}
],
"user": {
"id": "00deadbeef00deadbeef00deadbeef00"
},
"username": "whoever@wherever.net"
}
],
"activeAccount": "whoever@wherever.net",
"formatVersion": 2
}
I'm thinking that because the account can be faked anyway, I should just add the 'crack' -- unlimited offline mode profiles -- myself. Mojang and online mode servers won't let you log in with this, obviously. So there really is no harm... You can apply pretty much the same trick to the vanilla launcher and it works too - as long as you are offline.
everyone: thoughts?
Generally I am not against this. However I'm not sure how Mojang will react to this. After all it could be used to avoid paying for Minecraft if you don't intend to play on servers. On an upside it would possibly cut down on the patched versions of MultiMC which might contain malicious code, depending on who patched them.
Point is, you can already fool any of the launchers out there... it's hard to say what is right or wrong. Maybe we should just ask someone from Mojang.
I know, I have done it before. Entry in /etc/hosts
plus local webserver is yet another way. But officially supporting it is something else than having it an undocumented feature that was never intentionally added.
That sounds even more effective. Anyway, if the actual auth is involved, I believe that should be as locked down as possible. If only to be absolutely sure that we are actually talking to the right -- real -- servers.
Basically, fooling it with /etc/hosts
should be impossible. If that is allowed, then I'd see it as a security hole.
I do not want to leak any sensitive information to a malicious third party. I also want to remove the incentive for people to create these weird builds that can contain ... pretty much anything.
The main issue is that people with what I see as valid use-cases (admins testing stuff on offline servers, people who have valid accounts otherwise, but can't login due to being offline, etc.) are forced to use weird hacks.
How are you planning to implement this though, without opening it to allow arbitrary authentication. (Which is what a custom /etc/hosts entry would be for)
I'm telling you : that should already be impossible. How did you do it? You had to fake the SSL cert somehow...
I see what you mean now, right. Misunderstood you a bit.
I created my own modpack, but he's having a problem, look at the log: