4 ms·
The vanilla launcher will automatically patch 1.12 to 1.18, and 1.18.1 includes a specific permanent fix for it by switching to a newer Log4j version. There is
by creatonez 5y ago
The vanilla launcher will automatically patch 1.12 to 1.18, and 1.18.1 includes a specific permanent fix for it by switching to a newer Log4j version.
There is a workaround that fixes it for 1.13 to 1.18 only: Simply add `-Dlog4j2.formatMsgNoLookups=true` to your Java parameters
What about Minecraft <1.12? Well, Mojang employees have said on Twitter^1 to not use any Minecraft versions before 1.12 right now.
[1]: https://twitter.com/slicedlime/status/1469150995842310144 https://twitter.com/slicedlime/status/1469150995842310144
- cesarb 5y ago> The vanilla launcher will automatically patch 1.12 to 1.18 The patch seems to have been to the client-1.12.xml file, which I believe is the log4j configuration file for all client releases since 1.12, and the change seems to have been to add a {nolookups} flag to the log format (but I don't have an old copy of that file to compare and see if anything else was changed). If I'm not wrong, this gives a simple way to make sure your copy of Minecraft is patched: just check if that file has that {nolookups} flag.
- ginko 5y agoThis will be a pain for MC speedrunning where older versions are still quite popular AFAIK.
- tetha 5y agoWouldn't this be a breakthrough for the any% glitched category? You could just load + inject a class that makes you win instantly with only one chat message! <T C-V enter> speedstrat ftw. :)
- rcxdude 5y agoMC speed running isn't usually done on a publically accesible server though
- mainde 5y agoSpeedruners don't play on public servers I imagine?
- patrakov 5y agoThanks, this is the first message where I see the full instruction on where and how to apply the workaround. I was not even sure if this is something I should change in the third-party code that I run in a Docker container, and now I know it is just a change of the ENTRYPOINT or CMD line.