Minecraft Forums

Quote from Deereboy1998

Guys I think lately minecraft has been ripping us off. The mojang team originally said that the red stone update was due for late January. When it was late February, I wasn't surprised. That is what Mojang normally does...lies to our faces so we buy the game. They also said Mod API would be usable about 4 updates ago. I'm not surprised they say that we will get Mod API soon, that's what they always say. Don't trust mojang when they say soon. Jeb said that the red stone update would be out soon, so we are probably going to have to wait a while.

Quote from Wanderer

That sounds a lot more reasonable than the person who left the thread that I was replying to, but it's a good starting point for conversation, so prepare to receive a counter-argument!
All of the things you listed are proof-of-concept additions that were never before part of Minecraft. I'd say that some of them could have been "test runs" on new features they were coding into the engine, just to ensure that they worked.

For example, with the addition of Witches came code for localizing a mob to spawn inside of a very specific space (the witch hut) which very well could have come about because of bug-squashing or expanding the future possibilities of the Mod API. This means that mod makers can select mobs to spawn only in their mod-specific dungeon, for example, without the use of proximity-based and destructible mob spawners. Not only that, but they also mean testing and bug-squashing in the realm of splash-potion-based combat. (And you can't knock the Witch, it's the most annoying/deadly mob in Sethbling's craft bros PvP map)

With the addition of the Wither came the possibility of mob destroying explosion-proof or otherwise indestructible blocks. This could be something they felt was necessary for the Mod API, too, and the only way to properly bug-remove that kind of feature is to make it into part of the live game. Not to mention that with the Wither comes Beacons, localized application of potion effects from map features, also previously impossible and likely something they added as a direct result of determining what kind of functionality mod makers will need but obviously can't utilize unless it's implemented in-game (and this is also one of those GREAT additions for mapmakers- look at FVDisco's Sonic the Hedgehog map).

Fireworks give a great framework and (semi-)practical application of creating and using custom particle effects... But they're also very festive and once again something Mapmakers have used to their advantage (see: Evil Santa boss fight).

Bats... beats the crap out of me. I guess they're just atmosphere. But they're atmosphere I surely wouldn't opt to remove. They just feel like part of the game now.

An argument can be made that any updates - even updates you like - "aren't useful or wanted", as you put it. But perhaps, and I'm not saying it's the case, but perhaps these updates came around for deeper reasons we don't fully understand or aren't publicized.

Did you ever consider that most of the updates in 1.4 and 1.5 could be abstracted far enough to argue that they are simply implementations of new engine functionality they're developing to make the Mod API and coming future updates the best they can be?

When people talk about making the "wrong" kind of updates, do they ever consider that it is not the content of the update, but the code behind it, that is important to Mojang? I certainly never considered looking at it that way until I realized (while writing this post) that there HAD to be a reason for adding "witches and bats" - I would bet real money that it wasn't just a whimsical "Hey, let's add witches and witch huts!" There was an entirely new engine functionality added, and the point of an API is that it gives access to engine functionality without letting you write your own to avoid conflicts. Isn't it conceivable that witches were thrown in as an update just so that the "public" could test out the new functionality and work out bugs?

This is a long, involved process. That's all I'm saying. They set out to write the Mod API and realized that they could not possibly make it robust enough to support the mods that are out there without creating loads of new methods for achieving things like what the Witch or Fireworks added into the core engine functionality.

Quote from Nachtschatten

There's this thing I wonder about: How can 1.5 not be far off, considering there's still important things missing? Like the BUD block or Hopper filtering (which is kind of possible right now, but only by jumping through hoops. This is far from the simplicity of the Allocator.)

Quote from Sirsir94

You would have a point, if they hadn't broken WOOD!

...well you still have a point, but they BROKE WOOD!

Quote from Shourin

I post this every time there is a snapshot and i have submitted it to the bug tracker as soon as I found this white spaces that showed up since the introduction of the new block / item texture setup.

Screenshots

Seen in ALL Minecraft versions up till Snapshot 13w01a



After new texture setup in Snapshot 13w02a => 13w07a


However I have got no replies until the 13w7a snapshot by Random_Guy_32.


I ask if it was my graphs card then why does it show only in the snap shots newer than 13w01a??

I also found via reddit that other people who have kick a#$ beefy computers "High end gaming machines" also get this bug., "etho" This can be seen in one of etho's videos where he is building a game arena. A posted fix for Ati/AMD video cards does not fix this.

I also discovered that if you get a good angle on these cracks you can see what's on the other side. This could give people a unfair advantage if used in pvp related games. It's hard to do now but with optifine zoom it will be easy to abuse.

Quote from ProMinecraftVideos

Been waiting on name change feature for a long time now. The coding really isn't hard, so there must be another reason.