Eli Orona
- OroArmor
- JIRAUSER486382
- America/Los_Angeles
- Yes
- No
MC-234657![[Mojang] Gegy](../../../data/avatars/users/10122.svg){kind=small}
Main-Class entry in MANIFEST.MF isincorrect.Main-Class entry in MANIFEST.MF is points to non-existent class.
Manifest-Version: 1.0 Main-Class: net.minecraft.client.MainThis was taken from the beginning of the 1.17.1 Minecraft jar. The main class is at net.minecraft.client.main.Main. This is an obscure issue, but should probably be fixed.
Manifest-Version: 1.0 Main-Class: net.minecraft.client.MainThis was taken from the beginning of the 1.17.1 Minecraft jar. The main class is at net.minecraft.client.main.Main. This is an obscure issue, but should probably be fixed.
Manifest-Version: 1.0 Main-Class: net.minecraft.client.MainThis was taken from the beginning of the 1.17.1 Minecraft client jar. The main class is at net.minecraft.client.main.Main. This is an obscure issue, but should probably be fixed.
Main-Class entryinMANIFEST.MFis points to non-existent class.Unable to launch Client Jar using Main-Class entry from MAINIFEST.MF
Manifest-Version: 1.0 Main-Class: net.minecraft.client.MainThis was taken from the beginning of the
1.17.1Minecraftclient jar. The main class is at net.minecraft.client.main.Main. This is an obscure issue, but should probably be fixed.Manifest-Version: 1.0 Main-Class: net.minecraft.client.MainThis was taken from the beginning of the Minecraft Client jar's MANIFEST.MF. The main class is at net.minecraft.client.main.Main. This is an obscure issue, but should probably be fixed as launching the client jar directly does not work.
Unable to launch Client Jar using Main-Class entry from MAINIFEST.MF
This is just some quasiconnectivity.
Updated title
Yes. This issue is still present on 1.19.3.
Can confirm this is an issue as I noticed this while mapping the code for a modded toolchain.