I find this thread amoooooosing. You people complaining about this should stop having a cow! No doubt if this is a but with minecraft itself jeb will grab the bull by the horns and fix it by Monday, although if its because of the old texture pack then I think this problem aut to last until the cows come home.
that's hilarious I have not seen such a broken jar yet. the textures are inthe wrong location, which would be an easy fix for the user. I have not seen this myself. I just had a few rain issues. I am enjoying some real beta testing here. I feel like I am part of something bigger. The last time I got to beta test patches and what not was when drakan was released. That was fun.
Rollback Post to RevisionRollBack
"Yes, right. You're one of...those, Never understood why any self respecting Decepticon would choose automobile as his vehical mode when he could have flight." -Starscream
The 1.8 client has been out for a day and I'd say it's safe to say thousands(Supposedly a few million people who have bought the game, but certainly much lower than that amount frequent the forums, more specifically this one, so likely not anywhere near that amount know of the pre release) have been playing it. So far only ONE person has reported it on the forums.
I'm going to have to say this is probably a very VERY rare bug and not going to be something that would easily be found in the comparitively tiny amount of pre-beta testers they have testing it out before releasing it to the beta testers.
In other words, yes, an obscure bug like this that probably never once came up or made itself apparent to the in-house testers SHOULD have made it past development to the beta testers do actually beta test and report the error.
The "Beta" excuse is wearing thin now that they're getting close to when they want to "finish" the game. While it still applies enough that we shouldn't be angry about bugs like Moon-Cow, it does mean that Mojang should not Rely on Beta testers to completely debug they're game for them. And while Moon-Cow is indeed an obviously rare bug, it is one that should have been obvious in the code. The textures of everything that has it's own texture file is clearly defined within it's own code as being that file, and a bug that causes these textures to completely swap is quite blatant.
All of this is completely moot, because either the bugs in the pre-release were induced by the stress that was put o Jeb_ who has recently been in charge of the entire project while Notch does other things, or were intentionally left in in an attempt to get people who DO think "Beta = 'Early Play Time'" to shut up and let them work.
Thats astounding. BTW you can make the moon whatever you want it to look like if you go in the minecraft.jar and hit moon and replace the texture. PS: Terraria may have the blood moon calling in zombies, but nothing as fearsome as the cow moon........
The "Beta" excuse is wearing thin now that they're getting close to when they want to "finish" the game. While it still applies enough that we shouldn't be angry about bugs like Moon-Cow, it does mean that Mojang should not Rely on Beta testers to completely debug they're game for them. And while Moon-Cow is indeed an obviously rare bug, it is one that should have been obvious in the code. The textures of everything that has it's own texture file is clearly defined within it's own code as being that file, and a bug that causes these textures to completely swap is quite blatant.
All of this is completely moot, because either the bugs in the pre-release were induced by the stress that was put o Jeb_ who has recently been in charge of the entire project while Notch does other things, or were intentionally left in in an attempt to get people who DO think "Beta = 'Early Play Time'" to shut up and let them work.
I will now use Moon-Cow in a texture pack.
You're forgetting that thousands of players playing the game can find bugs faster than a small group of people, and people want the full release as fast as possible. Also, why would it affect ONE person? I highly doubt that it's much of a bug on their part, or their influence was very subtle.
Okay guys I just want to clear this up. I didn't touch any folders or the texture pack(yes I'm using the default) after my Minecraft went like that. All I did was restart my Minecraft, and that bug/error/glitch never happened again. I think it went like that, because of the severe lag I had while I was flying.
"my moon is cow,
your argument is invalid"
and you have started a new meme
/\/\ | /|/ |= ( |? /-\ |= ---|---
Are you using a texture pack? That might be causing the moo(n)...
The "Beta" excuse is wearing thin now that they're getting close to when they want to "finish" the game. While it still applies enough that we shouldn't be angry about bugs like Moon-Cow, it does mean that Mojang should not Rely on Beta testers to completely debug they're game for them. And while Moon-Cow is indeed an obviously rare bug, it is one that should have been obvious in the code. The textures of everything that has it's own texture file is clearly defined within it's own code as being that file, and a bug that causes these textures to completely swap is quite blatant.
All of this is completely moot, because either the bugs in the pre-release were induced by the stress that was put o Jeb_ who has recently been in charge of the entire project while Notch does other things, or were intentionally left in in an attempt to get people who DO think "Beta = 'Early Play Time'" to shut up and let them work.
I will now use Moon-Cow in a texture pack.
You're forgetting that thousands of players playing the game can find bugs faster than a small group of people, and people want the full release as fast as possible. Also, why would it affect ONE person? I highly doubt that it's much of a bug on their part, or their influence was very subtle.
(yea I did....)