I don't know how you can justify this. This isn't someone being an asshole on 2b2t... this is someone destroying thousands of small servers just to be destructive.
Most recently, the outrage was over the (entirely optional!) chat moderation features on private servers, and the mindless recitation that it would lead to widespread abuse and false-positive bans. It didn't.
I can only assume it's the result of non-technical people who know _just enough_ to think they know what they're talking about parroting misinformation in discords, Twitter, YouTube comments, etc. Perhaps it's a just a younger, more impressionable audience.
There is seemingly no reasoning with them either. They will vehemently defend wild points with zero evidence, and often with evidence to the contrary readily available.
It happens on HN a lot these days too on pretty much any Big Tech related topic.
It is true however that there wasn't really the wave of false positive bans happening that the community was expecting. At least as far as I'm aware.
[1] https://www.curseforge.com/minecraft/mc-mods/no-chat-reports
Spoiler: you can't because that scenario doesn't exist. It's a FUD bandwagon argument, nothing more.
> I run a server. Chat signing isn't enabled. Upon login, the user sees a message along the lines of "chat can't be verified on this server." Reporting doesn't work. Everything else works just fine.
are you a GPT or something
1. Chat moderation is *required*, unless you modify the vanilla game. There is no toggle for it on vanilla. You can choose to not enforce it for clients connecting to your server, but if they are a vanilla client they will sign chat regardless.
2. The initial wording of the rules that could result in a permanent ban, were incredibly loose & vague, allowing for bans for things such as swearing or alcohol/drugs, regardless of player age / legal status in their countries. This was something the community was able to change through pressure and the "outrage" you belittle.
3. > ...and the mindless recitation that it would lead to widespread abuse and false-positive bans. It didn't.
The reason it didn't was that since this community has a pretty tech-savvy sub-community of modders, we pulled apart that section of the code to examine it. And what we found was horrifying from a security standpoint.
Your message is signed by you (sig psuedocode in brackets):
"Want to play a round of spleef?"(JohnCrafter) "Sure"(jahsome)
Nothing, absolutely nothing in those initial few snapshots, ties your "Sure" to the context of a spleef match, or any proceeding chat. So with a burner account, one could change it to:
"The gays sure have ruined America, they must be purged."(BurnerAccount) "Sure"(jahsome)
It took several more snapshot releases before they started to actually implement a chain of context with signing, where one could prove what you replied to, or that a report had be adulterated. Again, psuedocode for how it's signed now after the "outrage":
"Anyone selling saddles?"(TexRanger) "Want to play a round of spleef?"(JohnCrafter+saddleMessage) "Sure"(jahsome+saddleMessage+spleefMessage)
4. The planned release schedule, and the "community consultation"
Something that seems missed to the history books, is that the development cycle for this was going to be one snapshot, one pre release, then release (In total, 2 weeks for community at large to see and respond before it's live to all)
That seems, rather short compared to most other previous releases that featured such a big feature? If it was adding emojis, sure. But a signature system, and full reporting framework? Turns out, from leaks, they had consulted a very, very small subset of the community under NDA on a private discord for about a year...
And it instead took 8 weeks to be launched. Due to the above mentioned issues with both the vagueness of planned rules, and the severe holes in the implementation as well as debate over the "stigmatization" being applied to unsigned chat messages.
One should also factor in that at this time, a prominent content creator within the community died. Which is never going to go well for "emotional stability" with young fans and likely contributed to some of the vitriol thrown about.
The Java community where much of this stemmed from, also has some trust issues with Mojang/Microsoft over previous debacles such as the ownership of Bukkit, and licencing around obfuscation mappings that were presented as a "here, use these to help with modding" but licenced very much more as a "look, but don't you dare touch".
And finally, Mojang had been, having issues shall we say, with their content release schedule up to that point (tl;dr the "Caves & Cliffs" update was understandably split in two during the start of the pandemic, but then further features from it slipped to the Wild update which even before chat reporting, had it's own drama surrounding "removed content" and reasons given by Mojang for it). Mojang had "used up" a lot of community goodwill before dropping a controversial feature in.
This in no way excuses the doxxing and personal attacks/threats levelled at the employees of Mojang. It was abhorrent and detracted from getting the real issues with this release/feature, resolved.
But at the same time, claiming it was all hysterics washes away alot of the problems with how it was implemented, and the sheer lack of consideration for the optics of adding a feature quickly with little to no public consultation, on a game that has been "public" in it's development for years.
If you don't want the update, don't use it...
Staying on an old version in perpetuity is often unrealistic.
subpar in the community's eyes ("concept art is not a guarantee", while true, was worded quite poorly. And the firefly's removed because some IRL are poisonous to frogs, a mob also added in the update.. they had this same issue with chocolate cookies and parrots years back, and both of those are in the game and done in a way to educate players.. they could have just made them not eat them, and give players who search for why a mini biology lesson, as they seem to want to do extracurricular stuff about mangrove swamps already..)
And I did not dictate development cycle... I discussed how they had had issues with the preceding updates to chat reporting, compared to before caves and cliffs where feature creep/scope had not exceeded their capacity to deliver. This was certainly before chat reporting, the main gripe and meme of the community (wild update being memed as caves and cliffs part 3... Etc etc)
And then pointed out the rather concerning, expedited release schedule, for a feature was both poorly communicated, and poorly implemented both in policy vagueness and security issues. Fake security is worse than no security as it induces complacency.
> To receive any update should be lauded by the community.
Patently false, if I worked at Roblox, and updated it to mine crypto, or access the webcam so marketing could run facial emotion analysis on the players... Well that's an update to a game, why are you looking so angry?? It was a free update.
There was a para/social contract between the community and mojang, it was strained by external forces before the chat report update, and broken by it.
We see the fallout of it with the latest update, mojang are much more quiet about features than previously until they are practically finalised.
They've split the community and shown clear hostility to people who aren't using Windows. What more do you need to conclude that Microsoft is "destroying" Minecraft?
Eventually, they released a "Windows 10 Edition", based on the Bedrock code base. This version is incompatible with Linux and macOS, and can't play multiplayer with the Java client.
Later, they renamed the Java client from "Minecraft" to "Minecraft: Java Edition", and renamed "Minecraft: Windows 10 Edition" to "Minecraft". They also started railroading buyers towards this game formally known as "Minecraft: Windows 10 Edition".
As a result, the definitive version of Minecraft, the version someone gets if you just tell them to "buy Minecraft", does not work on Linux or macOS. If you're a Linux or Mac user, and you want to play Minecraft with a friend who uses Windows, you're probably going to find that their game is incompatible with yours. Because as a Linux or Mac user, you don't get to play the version branded as simply "Minecraft". You're off in your own separate world, playing the incompatible game known as "Minecraft: Java Edition".
To add insult to injury, there's nothing technically preventing the game now known as "Minecraft" from working on Linux and macOS. "Minecraft Education" is a product based on the Bedrock code base which is available on Linux (well, ChromeOS) and macOS.
Does that make it clearer?
In any case, I don't see how any of what you described could be characterized as "hostile."
If you don't see how what I described could be characterized as "hostile", you've either misunderstood something, or we have a different understanding of what "hostile" means.
Indeed.
A company takes a game that had a very lively multiplayer community, replaces the game engine that was based on software that could run on any platform as long as it supported Java to .NET where the only possible platform is Windows. Take everyone who has ever purchased the game and force them to migrate their accounts to a Microsoft account in order to continue playing, then intentionally make the two versions of the game incompatible just to force people to play a watered down "definitive edition" that still lacks many of the features that allowed the community to thrive in the first place while issuing all these updates that essentially equate to "spyware".
Yes, I think the word you are looking for is, in fact, Hostile.
(Microsoft obviously have no intention of bridging this divide, but hobbyists manage to do it for free...)
Basically, it just further solidifies Minecraft players as the first-class citizens of the community and Minecraft: Java Edition players as second-class.
This comment is a great example of doing what you accuse others of:
-- makes grand claims without evidence being presented
-- accuses others of making grand claims without evidence being presented
Whilst also pre-empting any dissent by stating that any counter-arguments are "wild", and that people who aren't on your side are deficient.
It's bad logic and bad rhetoric.