mojira.dev
MCL-11030

Minecraft Indev levels refuse to load

I used to play Minecraft Indev sometimes, but since the laucher got updated at June 2019, levels (worlds) refuse to load or generate, and the game crashes or go back to the title menu. (Not sure if this was a launcher bug, but this happens since they got an update).
Though Indev versions are not in the laucher, they were original versions since I got them from the archive.

Comments 7

I have had the same problem. But here is a step by step way of fixing this issue.

  1. Open Minecraft Launcher

  2. Go into installations

  3. Click on the three dots icon on the indev version you want to play

  4. Click more options

  5. Go into JVM arguments and remove -Xmx2G

  6. Type -Dhttp.proxyHost=betacraft.ovh -Djava.util.arrays.useLegacyMergeSort=true into the JVM arguments

  7. Save 

Now you can play Minecraft Indev.

I'm skeptical. What would condone removing -Xmx?

I know it has been a long time since I have posted the solution, but let me explain. The reason why the indev versions don't work is the launcher is trying pull the versions and assets from a minecraft webpage that has since been removed. What the solution does is it redirects the launcher to a website that does have the versions and the assets. There are a few updates to this solution. 1. The website has been changed from betacraft.ovh to betacraft.pl 2. About your question, "What would condone removing -Xmx?" The answer is nothing. You don't have to remove -Xmx2G. How long this has been, I have no idea, but you don't have to remove -Xmx2G.

this isn't an issue with the launcher it's an issue with an outdated version having an error thrown due to the website data being down that it's trying to find.

A solution would be to have mojang create the data that it's looking for from their servers on the same website and domain it's looking for.

{Ismael Rosillo~} does workaround provided by Lazman321 works for you?

This ticket will automatically reopen when you reply.

At first didn't work, but I kept trying with other proxy hosts and found out that betacraft.uk (".pl" doesn't works anymore) is the current working proxy.

I'm still a little worried because they may keep changing their address, then it can stop working at any time, so I would have to search for the new address and change JVM argument manually.

Therefore, it is not the Launcher issue but the proxy of the host - as what I understand from your commentary. Closing the ticket as cannot reproduce.
If the issue persists and will be directly caused by the Launcher, please, create new ticket in the relation with this one.

ISRosillo14

(Unassigned)

Unconfirmed

world

Retrieved