1.7 packs?

[PhilHibbs]

I know, we haven't even got 1.6 packs yet, and already I'm asking about 1.7. Flame on!

But there's a serious side to this post - since 1.7 will be getting a whole new biome, and therefore new world gen and hideous chunk transitions (as well as existing witch huts no longer spawning witches), is it worth actually skipping 1.6 and waiting for 1.7 before starting a new long-term world?

 

[apemanzilla]

Considering that a lot of modders already have their sights on 1.6, and many are already done, I doubt they'll skip it, but it may be mostly just a beta pack like the 1.5 ones.

EDIT: Misread question, probably best to just wait for 1.7 for worlds.

 

[Indie]

I know, we haven't even got 1.6 packs yet, and already I'm asking about 1.7. Flame on!

But there's a serious side to this post - since 1.7 will be getting a whole new biome, and therefore new world gen and hideous chunk transitions (as well as existing witch huts no longer spawning witches), is it worth actually skipping 1.6 and waiting for 1.7 before starting a new long-term world?

I guess that depends on what you class as a "long-term world". Then when 1.6 comes out, will you want to skip 1.7 and wait for 1.8?

 

[Henry Link]

I don't know how much it may effect the modders code. But vanilla terrain gen doesn't overwrite existing chunks. It only comes into play when you travel far enough to generate new chunks. So any existing witch huts & spawners should still work.

 

[VikeStep]

What's wrong with making a long term world at 1.6? By the time a 1.7 pack comes out, I believe there will've been 2-3 months to work on a world. Unless you like to spend more than that on a world, it's always a better experience to restart at a major update, unless of course the worlds are compatible (which *fingers crossed*), 1.5 will be compatible with 1.6. The only problem we know will happen between 1.5 and 1.6 is that liquids will stuff up because of the new liquid code in forge.

 

[Omicron]

It's the same as with computer hardware. Whenever you consider buying, there's a new generation of something only two months away that will bring awesome features and performance. And after that was released? Something else will be just one month away! Better wait for that then!

Basically, if you wait until you have everything, you will wait forever and have nothing all the way there. If you need hardware now, buy the hardware that's available now. If you want a new world now, then start it with the packs that are available now.

 

[Riuga]

It's the same as with computer hardware. Whenever you consider buying, there's a new generation of something only two months away that will bring awesome features and performance. And after that was released? Something else will be just one month away! Better wait for that then!

Basically, if you wait until you have everything, you will wait forever and have nothing all the way there. If you need hardware now, buy the hardware that's available now. If you want a new world now, then start it with the packs that are available now.

Cept things like Windows 8.

Windows 8 is Developer's Hell.

 

[Bibble]

It's the same as with computer hardware. Whenever you consider buying, there's a new generation of something only two months away that will bring awesome features and performance. And after that was released? Something else will be just one month away! Better wait for that then!

Basically, if you wait until you have everything, you will wait forever and have nothing all the way there. If you need hardware now, buy the hardware that's available now. If you want a new world now, then start it with the packs that are available now.

This works fine, except for the "fringe" states. The times when you are thinking "I'd really like X new feature, but my current setup is functional". Then you have something during the wait, but are still liable to wait into perpetuity for the next big feature.

As with most things in life, you just have to make the decision about whether the benefits of waiting outweigh the amount of time that you are going to be waiting for.

 

[Omicron]

I said "computer hardware". Windows 8 is not hardware

 

[Bibble]

I said "computer hardware". Windows 8 is not hardware

No, but the example can be used for anything with a cyclic system, hardware, software, education, civilizations, social contact, the same arguments apply if there's both an up and downside to waiting.

 

[Riuga]

I said "computer hardware". Windows 8 is not hardware

I know. I was just saying.

 

[PhilHibbs]

I don't know how much it may effect the modders code. But vanilla terrain gen doesn't overwrite existing chunks. It only comes into play when you travel far enough to generate new chunks. So any existing witch huts & spawners should still work.

This is based on something that DocM said on his Mindcrack series, Dinnerbone had told him that 1.7 would stop his witch hut from spawning. I think that Minecraft doesn't store the "witch hut flag" in the chunk, but it dynamically calculates "This ought to be a witch hut according to terrain generation rules, so I'll spawn a witch here".

And more generally, I'm not suggesting that modders should skip 1.6 at all, just that a big change in terrain generation might make people want to wait.

 

[Golrith]

From our modded gameplay point of view, there's no point to skipping 1.6 for 1.7 for the few extra biomes and extra blocks, when it's already provided in one way or another in mods we already have.
There's no need for the modded game scene to always be at the current version of vanilla MC. MC updates always have a ton of updates after initial release, modders usually wait until the version has stablised, then the modders have to go through a few versions until their mod is stable. By that time, Mojang have then started announcing their next version.

The best thing is to wait for one version of MC and mods to stablise, then grab all the mods you want for that version, play it, then create a new world 2-3 MC versions later.

 

[PhilHibbs]

Yeah, I guess the more sensible option is to skip 1.7 as BOP and EBXL both add redwood type tree biomes.

 

[Gami]

I know, we haven't even got 1.6 packs yet, and already I'm asking about 1.7. Flame on!

But there's a serious side to this post - since 1.7 will be getting a whole new biome, and therefore new world gen and hideous chunk transitions (as well as existing witch huts no longer spawning witches), is it worth actually skipping 1.6 and waiting for 1.7 before starting a new long-term world?

1.7 sucks arse all it has is big flowers and some shitty mountains to stop easy traverse by horseback making the horse update shit.
Seriously all mods should be perched to release on 1.6 and stay that way at least till 1.8 because for the FTB community 1.7 is horseshit (you saw what i did there ).

 

[Grydian2]

Its going to be 6 months before there is a working pack for 1.7 MCP isnt even done yet. Let alone forge. Things are so different its going to be a learning experience for all the modders. You shouldnt skip 1.6 because honestly the jump to 1.7 is going to be so hard we might lose some mods in the process. 1.6 might the glory days of forge and modded minecraft.

 

[immibis]

1.6 might the glory days of forge and modded minecraft.

Wasn't that 1.2.5?

 

[Iskandar]

Yeah, don't wait for 1.7 packs. You'll wait a long, long time. It has already been stated that Forge won't be available for 1.7 until the new year, and it will then take modders a good two or three months after that to update, at the very least. And it will likely be an additional two or three months after that before 1.7 packs become available. I wouldn't be surprised if it was May or June before FTB has 1.7 packs available.

 

[xbony2]

I'm guess the 1.7 packs will come out in January. Not the 2014 January, but the 2015 January. No kidding, it's going to take a long time.

 

[MigukNamja]

It will be a looooong time before there are 1.7 packs that are as polished as 1.5.2 packs. Forge needs a major overhaul for 1.7, which will take months of coding and more months of stabilizing (bug fixes, tweaks). Then, mods will need to be ported/updated to 1.7, which will again takes months of coding and bugfixes and tweaks. I would not expect something as good as MC 1.5.2 Unleashed 1.1.5 for MC 1.7 until late 2014 at the earliest.

Heck, 1.6 is still not stable/complete. Most major mods aren't fully stable, i.e. as bug-free as their 1.5.2 versions.

The most stable platform today is 1.5.2 and if you're looking for a long-term platform, i.e. 1+ years, that would be 1.6.2/1.6.4 .