Mog (Ryan Holtz)

More than likely, Grum or Prof needs to add a call to GLStateManager.enableBlend(); before rendering ElytraLayer. Just guessing on the name here.

From what I recall, ItemRenderer calls GLStateManager.disableBlend() on its way out of renderStatic, which accounts for the issue being present in the first three listed cases. In fourth case, rendering the foil layer of armor probably disables blending on its way out.

All issues have been fixed, other than the "falling" particles issue. I will be filing a separate issue specifically for the falling particles issue, as this bug report is already effectively four different bug reports in one.

Please do not use the Minecraft PC bug tracker for reporting Minecraft PE bugs.

"Why do I waste my time debugging a game that isn't mine?" I don't know, but in the future please don't since you have no idea what you're talking about and your attitude downright sucks.

Unable to reproduce. See my attached two screenshots, one with me looking upward while against the border, one with me looking downward.

Please ensure that you do not have any pixels with an alpha value greater than 0 but less than 26 or so bordering the opaque pixels in the textures, as this will cause this issue. Please attach the resource pack or provide a download link.

Also cannot confirm. Are you sure your mouse isn't broken and is sending two clicks instead of one?

Bug report is wrong, anvils in 1.8 do not "take no fall damage". It will correctly progress to the next stage of damage each time you drop it, and it will disappear after you drop a Very Damaged Anvil. Works as intended.

Might be a modified server but the client still shouldn't crash when trying to render a null item.

6 is not a valid data value for Sandstone blocks. You must have obtained it with /give or some other means, because a Sandstone block would never generate legitimately in the world with that data value. Blocks with invalid data values are not intended to work.

If your account doesn't exist, it doesn't exist. Unless you purchased your account through mojang.com or minecraft.net, it's very likely that you purchased a hacked and/or pirated account which has since been deleted.

Please re-write your bug report. Note that under the "Description" heading there's still the default text which you did not fill in, and you for some reason put your entire bug report in the title. Also, it's "were", not "where". As in the past tense of "to be".

Sorry Liam, Daniel Mas gave you incorrect information. In order to generate a crash report, you first must hold F3 and C together for 10 seconds, then release them.

At that point a proper crash report will be generated, which you must attach to the bug using the "Attach Files" button, NOT by pasting it into a comment. Also, neither of the things you posted are crash logs, seeing the output of the game does not help us diagnose your issue.

You can rotate it into whatever orientation you want using just X and Y, having Z rotation as well is unnecessary.

The gif is too choppy to understand it. Please provide a better video, steps to reproduce the bug, and what your current world coordinates are.

Needs more info to be provided: Steps to reproduce, and at least one screenshot.

What on earth is "blockhitting"?

Re-check this one again with 1.8 final, I've at least fixed the "dropping 0-count items" bug. This one thus may also be fixed, since I suspect the cause of this one was villagers being able to pick up those 0-count item stacks.

You are straight-up awesome at finding interesting bugs!

What do you feel would be a good fix for this issue? As it's no longer possible to begin breaking a block while blocking with a sword, I think it should also not be possible to begin blocking while breaking a block. Your thoughts?

Has the latest snapshot or pre-release fixed the issue?