Comment on Minecraft's recent EULA changes place heavy restrictions on Java servers

LeylaLove@lemmy.fmhy.net ⁨1⁩ ⁨year⁩ ago

• Wilzax@lemmy.world ⁨1⁩ ⁨year⁩ ago

  Afaik they’re operating on an older version of the game and thus aren’t subject to new EULA updates unless they update to a version of the game that comes out afrer this EULA goes into effect

  source

  • Irisos@lemmy.umainfo.live ⁨1⁩ ⁨year⁩ ago

    Even if they updated to a new version, the hack client developers would probably just update their custom clients to ignore Mojang’s server ban list and call it a day.

    The new EULA is a joke and it’s easier to tell everyone to use a third party client (which is most of the time better than the official one) than try to abide to them.

    source
  • dual_sport_dork@lemmy.world ⁨1⁩ ⁨year⁩ ago

    In addition to that, I was told at one point that 2B2T doesn’t update to a more current version because some of the administration mods they rely on are not available for newer versions.

    source

    • kostel_thecreed@lemmy.ca ⁨1⁩ ⁨year⁩ ago

      Pretty sure it’s because of performance issues. 250 or so players loading chunks with a render distance of 10 chunks causes a shit ton of lag, even on their older, more optimized version of 1.12.2. They want to update to 1.19, but performance is the main reason they haven’t updated the game yet.

      source

      • yhvr@lemm.ee ⁨1⁩ ⁨year⁩ ago

        There’s been some promising advancements in the server space such as Multipaper and Folia to remove Minecraft’s single-core limitation, hence allowing for much higher player caps. I was on a Multipaper server running smoothly with ~300 players a few months ago.

        source
      • dual_sport_dork@lemmy.world ⁨1⁩ ⁨year⁩ ago

        That makes sense. And the Java editions have never been the most efficient thing in the world to begin with.

        source