I sure hope not. I would rather mod authors follow the actions of Mojang and take a version to work on performance. Imagine for a second that playing Monster had roughly the same FPS as vanilla.
That is because the Mojang employee that posted his FPS at the 32 chunk render distance is running a very high end machine with a i7 4770K and GTX 780. Its totally unreasonable to expect the average person to spend more than $900 on a computer just to hit that FPS.
I've always wondered why Mojang counts Minecraft as in full release, when it's constantly being updated. And honestly, I don't see their mod API coming out anytime soon. So I personally am against Mojang constantly updating the game. Just leave it at 1.8.I'm inclined to agree- a lot of the gameplay/design (all the 'stuff' we 'see/play') added has somewhat been sub-par, uninteresting and sometimes just absolute crap.
Better off cutting it out and leaving it to die.
However the internal changes- those proverbial nutshots to the modded community in the name of 'helping' us- might actually work
- which makes it worthwhile in the long run, but right now Minecraft is effectively in a state of perpetual alpha.
I don't follow snapshots because I personally think that so far all versions after 1.6.4 are crap. So... yeah.
Why not just start over from scratch?
- build 'Minecraft II' -fully redesigned/reengineered with modding/API in mind.
It better have been called "Craft & Mine"I actually started making my own Minecraft lookalike thing some time ago. With the engine written in C++ and the higher level stuff in python and a plugin/mod system that allowed both C++/python mods.
The chunk system worked but not much game stuff.
IMO, stable 1.7.10 packs will be possible within 2-3 weeks, maybe less. Meanwhile, it will be quite some time before we even get MCP, let alone Forge for 1.8.Personally I feel that by the time all the mods are ready for 1.7.10 and the official FTB packs are released it will be time to start migrating to 1.8