L
litten8
Guest
I feel like they should update once all the mods have updated, which will probably be a while, because not all of the mods they wanted have even got to 1.10.
I'm glad you brought that up. The difference is 1.8 never had a released FTB pack. Nor did 1.9. It wasn't because they were not good versions or that there was no forge. It was because they could update to the next version "super easy" Only all those alpha packs that got tested on all those versions never got played by the community the packs were being made for. Right now if they update to 1.11 even if it is super clean that is going to add to development time. Not to add in the fact we were already promised this would be the version for a while and that we we getting 3 maybe more 1.10 packs. Why not update is question of the day. What are you updating for. There really isn't anything in 1.11 that would be a good reason to update. You can use the current released forge version and still have stable packs. Al the work FTB has done for 1.10 will go down the drain. right now it will take 4 months or so to finish and released the 2 packs they wanted for 1.10 and then start developing 1.11 packs. By then 1.11 modded will be stable and there will be more selection of mods in 4-5 months. There is no point right now in going to 1.11. 2 mod dev doesn't equal the every mod dev out there. I have look at all the mods in beyond on curse I know how many don't have 1.11 versions. It isn't just 2 or 3. Someone explain how "we should cause we can" is a valid argument? I'm going to try that one on my wife next time she says she has a headache. If you already planned on 1.10 packs and 1.11 modded will be more stable in 5 months with more mods updated why update now. I will also point out that in my org point on this I posted that updating would be fine but that they would need to move beyond to 1.11 also or it is a wasted flag ship pack. I mean you are still waiting for 1.10 mods for God sake.
My comment was more in reference to FTb official packs. Sorry for the confusion. I played some very good packs in 1.8 and 1.9. I really like this one where you had a single chunk skyblock type one but can't rememeber the name.Actually, there were packs and Forge support for those versions... I made a few myself. The Mod Developers were the ones lagging the process during those versions, some declaring that they would never proceed beyond 1.7.10. Heck, many chose not to go past 1.6.4 because they didn't understand the benefits of changing from Static Block IDs to Dynamic.
I can see FtB's perspective on this matter as well as your points. Also, some people just can't handle change at a rapid pace. One thing to consider, however... There are new features coming in Vanilla all the time. As an example I saw a post about a new mod that adds rockets to Elytras/Gliders. This is already a feature in the released version of 1.11, and there are new things coming in 1.12 already.
As a former System Administrator I understand the mindset of remaining one update behind, so you only have to deal with the known bugs, but Minecraft is not Unix or even Windows and an Operating System needs to be more reliable than a mere game <GASP! HE SAID IT!> .
I'm all for updating, but I'm even more for settling on a stable platform for a while. Whether that's 1.10 or 1.11 doesn't really matter, I just want everything on the same page. As it is, I've submitted bug reports for some mods that have been fixed in 1.11 releases, but not 1.10, so I can't use them. Right now we have some developers only releasing for 1.10, some only releasing for 1.11, and some releasing for both. It's kinda frustrating.
So if FTB wants to push everyone to 1.11, I say go for it. As long as everyone else actually follows along and we don't end up missing out on half the content again. Just pick something and stick with it.
Most of what you said here holds true except that there is nothing FTB can do. They don't have to update to a new version. They can simple developed for a stable version for a while till after another big update happens. They choose to update or not and that choice is made by them. I will add for those reading the thread they have posted a transcript of the town q&a so you should check that out if you didn't get to see the video.Whie I can agree with that. The problem is not FTB. The problem is with Mojang and Forge. As long as they are updating we are always going to have a crazy roller coaster ride to play catch up. The only reason 1.7.10 was a stable and well developed is because we had a very weird stall in mod development world. Most modders didn't want to bother 1.8 or 1.9. It wasn't until 1.10.2 came out that they most of them started updating or putting out new content again. So unless there is another stall like that we will see this roller coaster ride again. And there is NOTHING we or the FTB team can do about it.
Oh is it so black and white. They could do what they always have done and disable features that are buggy or remove it all together like Ars Magica 2. And no one is saying stick with 1.10 we are say one when they do update to 1.11 to make sure the mods are there and that 1.11 is stable enough for modded and also that we are tired and update after update with no packs. As a modded minecraft player i don't need to be playing in the most recent addition I only need it to be stable and fun. FTB has already said they don't pick mods based on the Devs of the mods so what mods are in the packs are pick by FTB as a whole with. If a mod dev will not support the version they are on and the bug is gamebreaking out it goes for something else.@Magzie except there are things out of their control. Some mod devs out there that have already made the decision to stop fixes and support for 1.10.2 mods. So they have moved on. Which means the FTB team is now stuck with either keeping the pack on 1.10.2 with one or two buggy mods in it that will NOT be fixed or move on to 1.11.2. Your argument would be valid if he had a long 1.10.2 dev cycle. But that isn't the case. 1.10.2 will be a short lived dev cycle and as more mods jump to 1.11 fewer devs will want to keep support for both.