savagelung wrote:It's a community that can't be satisfied, and so the Mojang developers end up tiptoeing around it.
This is true, but that's ultimately true of the community for any successful game. You either need the devs to be isolated from that by a PR department (which is how most major studios handle it), or if the devs insist on interacting directly, you need to make damn sure the designers are strong-willed enough to not let it adversely affect their design decisions.
Basically, if you take the ballsy decision that Mojang has to interact constantly with the community, you need devs that are capable of (politely...which is where I differ as a non-corporate entity), tell the community to fuck off for their own good, and who have the confidence to be able to do that without a second thought.
We see this same story play out time and time again within the modding community where modders constantly trying to accommodate everyone ultimately leads to the destruction of mods, and that's with a very similar scenario playing out on a much smaller scale (even the largest mods have a tiny fraction of the total audience Mojang does).
But throwing some kids you hired to maintain what is an insanely popular game after the creator has left town into such a scenario with no experience in how to deal with it? Total madness. Seriously...no major game dev company would allow that to happen. I think the story of BTW illustrates just how rare it is that someone can deal with that kind of pressure, and that's based on me having a shit-ton of industry experience, me being an old fart that really doesn't give a shit how I'm perceived, me possessing what is largely an iron will when it comes to these things, and with a much smaller community to deal with...and still, I've struggled to keep my wits about me at several points in this mod's development.
I definitely don't envy the position of the current Mojang devs at multiple levels. How the current situation came about is really a circus-act when looked at in professional terms.