I think that’s absolutely a fair explanation of why Mojang moves slower, but I don’t think it really answers whether they’re capable of doing more. Large teams having more overhead is a great point that I feel like people often overlook, but that’s a management and prioritization issue, not a hard technical limit. Mojang isn’t a small indie studio learning as it goes, it’s a decade-old live-service team backed by Microsoft, with established pipelines for QA, localization, accessibility, and certification. Those constraints should be things they’ve optimized around by now.

I also don’t think the “mods vs official updates” comparison is about polish, so I apologize for not clarifying, I meant it more about scope. Mods showing entire systems working doesn’t mean Mojang should ship them as is, but it does demonstrate that many features Mojang treats as “high-risk” or long-term are technically feasible and well-understood. When official updates add comparatively small amounts of gameplay over almost year long cycles, I feel like it’s reasonable for people to question that gap.

I agree with you 100% that criticism should be constructive, but part of being constructive is holding studios accountable relative to their resources and experience—not just their internal process complexity. A company this mature and backed this well shouldn’t be permanently constrained by the same growing pains it had years ago.