Integration of Legacy Fixes (Skins, Sounds, and missing versions) from Betacraft

[WindowsXPSE]

Role

I am a long-term Minecraft player who enjoys both modern modded instances and the "Golden Age" (Alpha/Beta) versions. Currently, I am forced to switch between MultiMC and the Betacraft launcher because MultiMC lacks essential fixes for legacy versions.

Suggestion

I suggest that MultiMC implements (or allows as a toggle) the fixes provided by the Betacraft launcher. Specifically:

1. A proxy/fix for legacy skins (pre-1.6),
2. A fix for missing sound resources in Alpha/Beta, and 3. Support for archived versions (Indev/Infdev) that are missing from the official Mojang manifest.

Benefit

This would make MultiMC the true "all-in-one" launcher. Currently, playing Beta 1.7.3 or Alpha 1.1.2 on MultiMC results in a broken experience (no sounds, default skins, or crashes). By integrating these fixes, users wouldn't need to maintain two different launchers just to have a functional legacy experience.

This suggestion is unique

• I have searched the issue tracker and did not find an issue describing my suggestion, especially not one that has been rejected.

You may use the editor below to elaborate further.

Detailed Context

While MultiMC is excellent for modern versions, the "Legacy" experience is currently lacking compared to specialized launchers like Betacraft (https://betacraft.uk/).

The main issues that need addressing are:

• Skin Support: Legacy versions use an old API that Mojang took offline. Betacraft uses a wrapper to restore skins; MultiMC could implement something similar.
• Sound Resources: Many Alpha/Beta sounds are not correctly downloaded by the official manifest.
• Version Archive: Many historical versions (like early Indev or specific Infdev builds) are missing from the default list but are highly valued by the preservation community.

Integrating these features would bridge the gap for players who want to keep their entire Minecraft library within the clean, organized UI of MultiMC.

[phit]

you can use the betacraft proxy in multimc and old versions can be added manually, its unlikely MMC5 will ever add versions that aren't in the official launcher

Betacraft proxy reference copied from their Discord discord.gg/d4WvXeQ, all credits to them and keep in mind you have > to trust them to use this. No association to MultiMC or warranty are given by us, use at your own risk.

Pick your target game version and add them to the instance java arguments.

c0.0.13a to c0.30-c-renew:
-> -Dhttp.proxyHost=betacraft.ee -Dhttp.proxyPort=11701 -Djava.util.Arrays.useLegacyMergeSort=true

in-20091223-1459 to a1.1.2_01:
-> -Dhttp.proxyHost=betacraft.ee -Dhttp.proxyPort=11702 -Djava.util.Arrays.useLegacyMergeSort=true

a1.0.8:
-> -Dhttp.proxyHost=betacraft.ee -Dhttp.proxyPort=11703 -Djava.util.Arrays.useLegacyMergeSort=true

b1.3-demo:
-> -Dhttp.proxyHost=betacraft.ee -Dhttp.proxyPort=11704 -Djava.util.Arrays.useLegacyMergeSort=true

a1.2.0 to b1.8.1:
-> -Dhttp.proxyHost=betacraft.ee -Dhttp.proxyPort=11705 -Djava.util.Arrays.useLegacyMergeSort=true

b1.9-pre1 to b1.9-pre6:
-> -Dhttp.proxyHost=betacraft.ee -Dhttp.proxyPort=11706

1.0.0-rc1 to 1.5.2:
-> -Dhttp.proxyHost=betacraft.ee -Dhttp.proxyPort=11707