-
Bug
-
Resolution: Fixed
-
2.4.57 (Win 10/11 App), 2.4.69 (Win 10/11 App)
-
None
-
Confirmed
-
1043837
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.