This happens as part of the new skin fix here. Probably no one uses Java 7 to run this, but it's worth keeping compatibility due to weird old Java programs relying on outdated behaviour sometimes.

I have enjoyed this fork of retrowrapper and I thought about this feature. (NOTE: This is a Suggestion not a bug!)

Very annoying and defeats the purpose entirely.

Noticing this consistently with wrapped b1.9pre6.

"When you teleport to an extremely high value in inf-20100227, then the game crashes. I tried the 32-bit integer limit using RetroWrapper and the game instantly crashed. When you start the game back up, it instantly crashes before it can even take you to the title screen in the same way. Disabling cheats fixes this, but when you turn cheats back on, it happens again. Perhaps RW somehow saves coordinates from the previous session and uses them when you start the game again?" - MisterSheeple

Using RetroWrapper + MultiMC Offline removes multiplayer support.

Error Message:
java.lang.IllegalArgumentException: Comparison method violates its general contract! at java.util.TimSort.mergeHi(TimSort.java:899) at java.util.TimSort.mergeAt(TimSort.java:516) at java.util.TimSort.mergeCollapse(TimSort.java:439) at java.util.TimSort.sort(TimSort.java:245) at java.util.Arrays.sort(Arrays.java:1512) at java.util.ArrayList.sort(ArrayList.java:1464) at java.util.Collections.sort(Collections.java:177) at e.a(SourceFile:926) at ip.c(SourceFile:342) at ip.b(SourceFile:284) at net.minecraft.client.Minecraft.run(SourceFile:607) at java.lang.Thread.run(Thread.java:748)

Now that I have your attention, I'd like to propose that we remove RetroWrapper from the FAQ, as it's now been inactive for a year.

Its only detecting Alpha 1.0.16
I have way more versions than that (I want to wrap inf-20100320 specifically and it cant detect it)
I dont know anything about why this is happening
help

e.g. optionally removing the 32 million limit from inf 0313-b1.7.3 and the 30m limit for later versions. If this ever supports snapshots then it'd definitely be interesting to see how 14w30a/b behave at a billion blocks out.

Not sure if this is out of scope since it would require jar modding.

Once I open up the wrapper version (I am doing this on the first build of infdev) it crashes, I have tried with many different versions, and the same output comes. Please help!

So I started up retrowrapper and it crashed. For me on MacOS 11.6.3. I had an installation of java 17.0.1 which could be the reason why it crashed. The newer versions that you made do not start and give me a java boot error after 10 seconds from starting it. I went to even older versions made on xa's repository and those booted but it gave me an error that said null and so it didn't work. Here is me reproducing it:

Potentially also out of scope since it would likely require directly modifying the game somewhat, but many skins which rely on 1.8+ rendering look weird in versions prior to that point.

RetroWrapper does not handle cape URLs. The fix would be similar to the skin fix. Needs more investigation.

BetaCraft manages to do this so I think that it would work well for this, as the only way that I can connect to classic servers without BetaCraft is by using ViaFabric, which is super unstable and typically doesn't work well.

Hello,

The skin preview in inventory resets to default steve after death, or a long period of time (probably not)
I was playing alpha 1.2.6 on the newest version of retrowrapper installed.

Can somebody help me out?

The game crashes instantly on any version with a 1-file save format when using Single Player Hacks.

"All versions before Alpha 1.1.2_01 (Sound bugfix) have wrong and missing sound effects." - yellowwinner
"January Indev not playing sounds. Versions in-20100111-1, in-20100125-1, in-20100125-2, in-20100130 and in-20100131 don't play any sound. c0.30 and in-20100203 play sounds like other versions." - yellowwinner
"No sound in inf-20100415 without wi-fi connection." - Gruby5588

Actions to take:
"Need to parse client version somehow and send sound definitions depending on it." - kcxx

As in the title, launching the wrapped instance does absolutely nothing diffrent from vanilla, inf-20100325 blackscreens after pressing "Create" in the world generation screen, same with any version before it, sometimes the world loads but any movement attept makes it go to the blackscreen.

EDIT:
After updating GPU drivers (Nvidia, game ready driver) if minecraft is left on the black screen for too long (earlier nothing happend) it starts trying to render something, when that eventually fails it crashes and soon the whole computer follows, with an error code that seems to refernece some issue with graphics buffer/GPU RAM

"Looks like it only does that while you are moving. JFrame updates are the cause." - kcxx

The guide in the description of this fork is only for the official Minecraft launcher. I want to install this onto MultiMC since it is way easier to control different versions there and much more that is more of a personal choice. There isn't a .json file in the MultiMC launcher that's anything like the one in the official Minecraft launcher. Also, I think it would be nice to have an option of where you install the wrapper. Like, installing it in MultiMC or the official launcher or TLauncher or any launcher really. It would be pretty convenient and easy as you wouldn't have to deal with launcher specific quirks on your own and install it manually.

Running RetroWrapper with the --workDir flag does not use the specified directory as the minecraft directory / RetroWrapper does not let you choose which directory to use as the minecraft directory.

The installer does not let you choose the minecraft directory to instal to / uses hardcoded values which may not work on some systems.

When making a level in 0.30, there are very noticeable framerate drops after loading a save file. If this gets fixed I will be very thankful for that. Example: Before Saving and Loading Save

(94 fps)
After Loading That Same Save:

20 - 40 fps

After some research, apparently there are areas in the world that cause massive spikes of lag. FPS above 60 does persist as usual but the 20 - 40 fps issues happen if I look in that area.