The Bug:
Using a custom older version of Minecraft (without mods) results in a broken game state, preventing proper launching and causing a soft lock. I followed the instructions in https://www.reddit.com/r/MinecraftHelp/comments/tghe80/java_how_can_i_access_beta_16_test_build_3/.
Steps to Reproduce:
Navigate to the ".minecraft" folder and go to the "versions" folder.
Create a new folder called "b1.6-tb3" (without quotation marks).
Visit the following wiki page: https://minecraft.fandom.com/wiki/Java_Edition_Beta_1.6_Test_Build_3
Click on "Client" under the "Downloads" section to download the "b1.6-tb3.jar" file.
Place the downloaded "b1.6-tb3.jar" file into the newly created "b1.6-tb3" folder.
Right-click on ".json" on the wiki page, select "Save As," and save it as "b1.6-tb3.json" in the same folder.
Open the Minecraft launcher (close and reopen it if it was already open).
Go to the "Settings" tab and ensure "Show historical versions" is checked.
Click on "New installation," give it a name, and open the "Version" dropdown menu.
Scroll down to the section with versions starting with "old_beta" or "old_alpha".
Select "old_beta b1.6-tb3" from the list, save the installation and click "Play".
→ ✔ The game launches with the newly created version.
Observed Behavior:
Upon launching the game with the custom older version, Minecraft displays an error message stating it cannot run and becomes stuck in a loading state. The "Play" button remains unresponsive until the launcher is restarted, resulting in a soft lock.
Expected Behavior:
When launching Minecraft with the custom older version, it should load and initialize the game normally, without encountering any errors or getting stuck in a loading state. The "Play" button should function properly, allowing gameplay to proceed without requiring a launcher restart.
Attachments
Comments 6
Hi there!
Can you write more about your custom Java version?
Can you give us a reprosteps for this?
Can you also upload launcher_log file from .minecraft folder?
Please also uninstall the Launcher, delete .minecraft folder (copy its content elsewhere before deletion) and then reinstall, restart your computer. Then please try to boot the Launcher.
This ticket will automatically reopen when you reply.
Well I was trying versions I downloaded from the forum. For the update I was trying to run 2 different updates (Separately of course!) and those updates were beta 1.6 test build 3 and the 2.0 april fools update. Both of them failed. (I don't know witch log so I uploaded them all. lol)
Hi again, I updated your ticket with repro steps and tried to reproduce your problem.
I could not reproduce your behavior. I followed all the steps from the reddit post and was able to launch the desired Minecraft version without any problems.
Please uninstall the Launcher, delete .minecraft folder (copy its content elsewhere before deletion) and then reinstall, restart your computer. Then please try to boot the Launcher.
If the bug persists, please upload only the most recent laucher_log file in which this error occurred.
Hello there! Thanks for providing the necessary information. In the future, please post a comment instead of editing the report for updates like this.
Your launcher_log file says "Unable to download https://s3.amazonaws.com/Minecraft.Download/indexes/legacy.json to <WORKDIR>\.minecraft\assets\indexes\legacy.json". This file has been on my system since 2018, but when I remove it, I receive the same error as you.
Help please? I tried to run minecraft version 2.0 and minecraft just crashes. (Does not softlock me though phew.) I uploaded the crash report to! To recreate just follow the steps above except replace the test build with the 2.0 update on the forum. Yes it's a little off topic but still it's pretty similar.
We do not have enough information to find the cause of this issue.
Please attach the full launcher log found in
[minecraft/launcher_log.txt|https://minecrafthopper.net/help/finding-minecraft-data-folder/].Just a reminder, to make your bug report as effective as possible, please try and include the following steps to reproduce the problem:
If your ticket does not look like the example given here, then it's likely to be closed as incomplete.
This issue is being temporarily closed as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki