Comment on Minecraft is removing code obfuscation in Java Edition
oxysis@lemmy.blahaj.zone 1 day ago
Oh I see it’s that time of the year where Mojang gives the community a bone after stomping on them the rest of the year.
Anyways as someone who has worked on Java projects extensively since 2020, very little will actually change from this. The main problem of Mojang’s asinine version numbering will continue to be a problem for any modding, server, building and resource pack projects past 1.19.
Fuckin right?
ALSO can Mojang get my goshfuckin ALPHA account back that Microsoft deleted because I wasn’t paying attention to their bullshit during COVID and now it’s gone forever even if I make a Microsoft account which I will never do and now I have to pay money to Microsoft (which I will also never do and have never done)?
Go join mc: consequences edition discord.gg/mojanglawsuit (Website link in case you don’t wanna use discord: lawsuit.gg)
Kelly@programming.dev 1 day ago
They do what now?
JustARegularNerd@lemmy.dbzer0.com 1 day ago
Previously, they had the versioning system 1.MAJOR.MINOR, where Major referred to a feature update, and minor referred to bug fixes or other non-breaking technical changes
The first instance where they broke this was 1.16.2 by adding the Piglin Brute, but this was so minor that hardly anyone really cared, and hey, free feature with a minor update!
Well, now they have update “drops” where the minor version means either what it used to, or it’s also a feature update, just not as big as a full update.
From the wiki:
1.20: Trails and Tales Update 1.20.3: Bats and Pots Drop 1.20.5: Armored Paws Drop 1.21: Tricky Trials Update 1.21.2: Bundles of Bravery Drop 1.21.4: The Garden Awakens Drop 1.21.5: Spring to Life Drop 1.21.6: Chase the Skies Drop 1.21.9: Copper Age Drop
oxysis@lemmy.blahaj.zone 1 day ago
That’s close to how the numbering system works! It’s MAJOR.MINOR.PATCH, Mojang just doesn’t use the major part at all.
Also I completely forgot the piglin brute existed!
mercano@lemmy.world 1 day ago
It’s kind of like Java itself, Sun dropped the leading 1 after 1.4, following it up with Java 5.
themagzuz@lemmy.blahaj.zone 22 hours ago
the problem is that the way version numbers are handled now, it’s more like 1.MAJOR.MINOR, with no real definition of what counts as a “minor” update, so it’s hard to tell which versions are compatible. i feel like this problem would mostly go away if they either added another number to the version to signify patches, or actually used semver properly (they could mix these approaches to do something similar to java, so the next version would be 22.0.0)
i feel like this whole version debacle is only gonna get worse because microsoft is planning to move to a “content drop” model, with smaller more frequent updates, which means even more pressure on the “patch” version. so unless their update model or versioning systen changes, we’ll probably be playing 1.21.37 in a couple of years, and good luck figuring out which of those versions are actually compatible
oxysis@lemmy.blahaj.zone 1 day ago
Mojang started adding in substantive resource pack changes in the patches for 1.19. Which made it more annoying for resource pack artists to support the update their since it required 2 separate versions of a pack to be made and maintained just to make sure it works properly. Let alone the annoyance of having to constantly deal with people complaining about it not working when it is an issue Mojang made.
There is also Mojang’s censorship of their community that began in the 1.19 patch versions which allowed Mojang to just ban anyone for saying something they didn’t like. Servers largely just disable it since it’s a headache to deal with and it doesn’t benefit them at all, only Mojang.
Then in 1.20 and 1.21 Mojang began adding content in the patches so it makes it a nightmare to support the patch versions since they now function differently than they used to. Which only makes it harder for servers to update and makes the experience of joining servers more frustrating. So plenty of servers on those updates just blacklist certain versions just to make sure things are able to function.
Oh and at some point Mojang added censorship to player skins. And it can be triggered by just mass reporting any individual skin for any reason.
Basically Mojang made a fuck ton of problems where none needed to be or used to be.
oxysis@lemmy.blahaj.zone 1 day ago
Also I just want to add this, but I was sounding the alarm on the patch version problem back in the 1.19 days. The community at the entire either ignored me or called me crazy for pointing out how it was problematic. Now the community is growing more and more annoyed and I’m just sitting over here saying I told you so.
I’ve mostly stopped playing the game because of Mojang’s constant shitty choices and because of the community refusing to call Mojang out on their bullshit.
Truscape@lemmy.blahaj.zone 1 day ago
The no chat reports mod and having community hosted servers that don’t really need to give a damn about what Mojang thinks (I’ll convert my server to support cracked accounts if I have to) kind of pulls the heavy lifting to allowing players to keep playing without having to give a shit about overall moderation by the company.