Okay, so...in light of 1.12 being released, can we not do what we did with 1.11?
I've gotten a fair bit of flak about jumping ship to 1.11 so early. You know, it never would have been a problem if I hadn't been one of the only more-downloaded devs who updated.
There were few excuses with 1.11. I know a few mods (namely Ender IO) that have a lot of internal systems involving item management ran into problems, but that's a very niche case -- even heavily item-centric mods like Refined Storage were able to update. The null ItemStack change wasn't that big of a deal. At worst, across the 5 mods I've ported to 1.11, the process took about 8 hours of solid work. At best, in mods like Ice and Fire, it took 2-3 to get an initial buggy port going, though the dev wanted to fix some previously-introduced 1.10 bugs before releasing it.
So where are we now? Despite a fairly easy update, quite a few of the largest mods still aren't on 1.11, and though many have updated quite recently, their stability can be questioned. Had we updated to 1.11 much more rapidly, there would have been a chance for mods to stabilize themselves before moving on. Now, we're hitting 1.12 at a pretty unstable time.
Look, I get the argument that updating quickly is "leaving players behind" or "making life very hard for modpack makers". But it's a necessary evil. As I've addressed in responses elsewhere, there's a very clear vicious cycle: if modders don't update because there aren't enough players, pack devs won't update because there aren't enough mods, and players won't update because there aren't enough packs. Ultimately, the community never updates, even on a fairly easy version change like 1.10 to 1.11. Of those three groups, only modders have the capacity to break the cycle at first: pack devs need at least some mods to be present, and players can't be expected to play on a version with less selection without some particular modder-created benefits. So unless modders take the risk (hint: it's not actually a risk -- if your mods are fairly stable, it's not like they won't be used on older versions) and push their mods to 1.12, we're never going to see the countless code benefits and less-importantly new vanilla features that have been introduced.
So please, as an address to all the devs out there, especially those who haven't updated to 1.11 yet, please let's not make 1.12 another version to fracture over. It should be a trivial update by all accounts, but hell, there's people out there who couldn't even be bothered to change the version number on their CurseForge projects from 1.9 to 1.10. The sooner we all update, the sooner pack devs and players can move on and we can have a new "plateau" version with a lot of development for it. Let's not have another 1.11 where divisiveness over updating created a version where the mod selection only recently became viable despite 1.11 having been released over six months ago.
Sorry if this is a little pithy, but I rather like stable Minecraft versions and hanging around in 1.10 helps nobody in the long run.
Posted Jun 7, 2017, 1:23 PM UTC · edited