Cloudy (Aaron Mills)
Comments
No one said get a better computer. Your graphics drivers are prioritizing the integrated graphics chip inside your laptop, instead of the dedicated graphics hardware. Fix it so that minecraft/java is a priority, and you will find it works perfectly.
FYI, the resource system could not possibly cause the kind of lag you are claiming it does.
A modded hacking client, would not prevent this - as a modded hacking client would just say "Yeah, I'm Vanilla"!
Anyway, this does not reference a specific bug or behavior - as such it is invalid (and is more akin to a feature request).
I will also add that this bug tracker is only for unmodded clients. In future please do not report any bugs to do with modded clients.
This is working as intended. Pistons are not supposed to be able to push Obsidian or Bedrock.
This ticket is invalid as it relates to a modded or 3rd party client/server.
Any non-standard client/server build needs to be taken up with the appropriate team, not Mojang.
Any plugin issues need to be addressed to the plugin creator.
This site is for addressing issues related to the base unmodded MineCraft.
I also cannot reproduce this on vanilla.
This is a technical support issue; this site is for bug reports only. For technical support please use the Mojang Support Center.
However, I'm pretty sure this is an issue with Java 7 under Mac OS X - downgrade to Java 6. Please see the support section for any further queries.
Crash log please! And more information. Does it happen all the time, or did it just happen once?
Are you sure your hunger bar wasn't low? Do you have any further information?
I'm closing this as incomplete - if you can provide more information, please open another ticket.
Spam Golem is correct, marked as duplicate.
This ticket is invalid as it relates to a modded or 3rd party client/server.
Any non-standard client/server build needs to be taken up with the appropriate team, not Mojang.
Any plugin issues need to be addressed to the plugin creator.
This site is for addressing issues related to the base unmodded MineCraft.
If you can replicate the issue on an un-modded client, and provide a crash log, by all means please create a new ticket.
Note: Speak for myself, not Mojang. puts on modders hat
@Rickard: He provided MCP code. MCP code has different namings. That's why it didn't work - it is sometimes hard to see what variable you're referring to. And that type of attitude isn't going to get it fixed any quicker.
@Dalton: They obviously didn't ignore the fix. See above about namings. Decompiled and renamed code != actual vanilla code.
Duplicate of MC-1865 , please use the search function to see if your bug has already been submitted. Currently over 25% of tickets are being closed as duplicate.
Duplicate of MC-2497 , please use the search function to see if your bug has already been submitted. Currently over 25% of tickets are being closed as duplicate.
Yes, the game considers them transparent.
Note: I speak for myself, not Mojang.
To those people who are saying "How could you let this bug through!!!!!". Bugs happen. It was found before release, but fixing it before releasing would have caused further delays (modders already had to update to 1.4.3 and then to 1.4.4). This is a small rendering issue - barely noticeable (at least for me). I imagine that they thought it was a minor enough bug to release - certainly better than a few of the crashes in 1.4.2/1.4.3.
I just crashed with the same error while trying to join my own lan game - so this is confirmed. I will note that it was also completely vanilla.
There is nothing more that we can really say on this matter. All these issues are mod issues - they don't happen in vanilla Minecraft and as such we cannot be of further assistance. I do hope you manage to come to a resolution of your issue though.
Can you provide any more information please? The seed of the map for example?
I'll just put my two cents in as to WHY downgrading is a bad idea, and why it isn't a bug that if you go back to a previous version, items are missing.
Updates may change the data format on disk as to how the world is stored - including items, blocks, etc. That is perfectly fine to do in an upgrade, providing it retains compatibility with older worlds. It is not, however, possible (or needed) to guarantee compatibility with the reverse. It would be unrealistic to never change the data format storage purely so that the first Minecraft alpha could still read the worlds. Granted, this is 1.8 to 1.7 - not a big jump as in the circumstance I mentioned. However the same principle still applies.