Technic News

Launcher

Log4j vulnerability fixed in launcher build 707

The log4j vulnerability has been fixed in the latest build of the launcher (707). Just restart it and you'll be updated automatically. **It's incredibly important that you get this update.** With this update you'll be safe again. So what did we do? Well, it depends on the MC version. - log4j 2.0-beta9 gets replaced with a patched version (2.0-beta9-fixed) (MC >= 1.7 < 1.12) - Any other log4j version gets upgraded to 2.15.0, the one that isn't vulnerable (MC >= 1.12) - -Dlog4j2.formatMsgNoLookups=true flag was removed, since it wasn't needed anymore If you run the `${date:YYYY}` test on this, you'll get the `2021` text. However, if you try the actual vulnerability (the JNDI one), it won't be parsed. Thanks for the patience and have fun!

Launcher build 693

**Launcher stable update** (build 683 to **build 693**): - Minecraft process exit code is now logged ("Process exited with error code N") - The launcher will now display an error at startup if running inside OneDrive - Fixed an issue with large downloads resulting in a negative progress bar (-2147483647%) - Dependency updates

Launcher build 656 released!

Build 656 has been released to the stable update stream. We've added: - **Support for custom Java JVM arguments** (remember that giant box in Java Settings labelled "Java Args"? Well, now it works) - **Support for wrapper commands** (so you can use stuff like optirun in Linux) - Oracle Java runtimes previously had no vendor name. Now they show up prefixed with "Oracle". - The Java detection is now smarter on Windows and supports more vendors and locations. - Probably not a huge deal, but the launcher now correctly identifies arm64/aarch64 as a 64-bit platform. Have fun!

Support for Microsoft accounts is now available

It's here! We have pushed support for Microsoft accounts into the stable channel of the launcher, for testing. There might still be some bugs we haven't found yet.

Let us know of any issues you might find in our Discord, in the #tech-help channel, but we hope it works without any problems!

If you were previously using the beta channel for MSA support, you can now switch to the stable channel in the launcher settings.

Have fun!

Support for 1.13+ Forge is here!

We know it took a while, but it's finally here.

Technic Launcher now supports Forge in Minecraft 1.13 and above.

We're using the same wrapper MultiMC uses (https://github.com/ZekerZhayard/ForgeWrapper), and the necessary changes have been made to our launcher all thanks to phit.

But how do you use it?

Well, instead of putting the Forge universal jar as your "bin/modpack.jar", you put the Forge installer jar. That's it.