this post was submitted on 18 Feb 2026
71 points (96.1% liked)
PC Gaming
13938 readers
372 users here now
For PC gaming news and discussion. PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments, within reason.
- Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
There are a lot of modpacks which are already tied to specific versions of the Minecraft client. Unless I'm missing something, those would be unaffected. What is affected are mods targeting the bleeding edge builds of the game. I expect that the longer effect, if any, is reduced mod support for those newer builds.
But as for this:
Lol apple
Ah right, they hard forked Vulkan and then called it something else, just for the fuck you.
With compatibility layers being what they are these days I don't think it's going to be too much of a problem.
AFAIK all modpacks are made for specific versions of Minecraft, so the current modpacks are completely unaffected. And even for future modpacks, the modpack creator doesn't need to care too much about this, since it'll affect the mods directly. (A modpack is, like the name says, just a pack of mods stitched together and glued with some configs.)
Plus popular modpacks are often for extremely old MC versions; for example a lot of people still run modpacks made for 1.16.5 (4yo), 1.12.2 (8yo), or even 1.7.10 (12yo).
Yup, i use Prism launcher or Atlauncher and play a number of modpacks mostly older versions. It's no biggie.