• circuitfarmer@lemmy.world
    link
    fedilink
    English
    arrow-up
    33
    arrow-down
    1
    ·
    edit-2
    1 day ago

    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:

    While Windows and Linux machines, with GPUs that are less than 10 years old, can run Vulkan just fine, macOS doesn’t officially support this API either

    Lol apple

      • buddascrayon@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        36 minutes ago

        With compatibility layers being what they are these days I don’t think it’s going to be too much of a problem.

    • Lvxferre [he/him]@mander.xyz
      link
      fedilink
      English
      arrow-up
      13
      ·
      24 hours ago

      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).

      • FreeBooteR69@lemmy.ca
        link
        fedilink
        English
        arrow-up
        1
        ·
        58 minutes ago

        Yup, i use Prism launcher or Atlauncher and play a number of modpacks mostly older versions. It’s no biggie.