yarrmateys

it may be intended, but it may as well be something that was missed when the trees were upgraded from all hardcoded values to the new method.

the new ones use the newer method as well as far as i know.

note, if you really want to save that world, but don't have any backups and you didn't do much with new 1.9 stuff, you can open the world in 1.8 and quickly save it to downgrade its version, then open that world in mcedit and remove every sign/book manually.

the first part of this report is not a duplicate.

the dupe link goes to an invalid report (calling an easter egg a bug), which is unrelated to the first half of this bug report.

this bug is about the small zombie/pig zombie being offset up, so they're floating in mid air instead of having their heads touching the floor like every other mob does.

it happens to more than just block placement/breaking.

while i see this on those as well, i also get the same problem when interacting with stuff like doors or gates. the visual will still show closed door/gate, but i can now walk through it.

the crash was fixed.

the first part wasn't as much of a bug as it was an useless feature without the accompanying ground level setting.

but that's probably more of a feature request so i doubt that part applies here, so yeah, it's fixed.

wouldn't it be consistently affecting the same chunks until you forced them to appear then?

in my case when i go underground in spectator mode it'll flicker. when i turn around big chunks of visible caves and other stuff will blink, appear or vanish.

easiest to notice by going into spectator mode, then flying underground into solid rock.

the caves will be flashing in and out while you're down there.

one way to circumvent it until fixed would be to rename the newly created world on creation if previous wasn't deleted completely and its folder/files still exist.

say, you make world called "new world", then delete it (but deletion fails) and make a new one called the same. instead of calling its folder "new world" too and causing the bug, just auto rename it to "new world_1" or involve a date+time, like "new world_20140723151905" to prevent multiple attempts to create the same name.

that way even if the world fails to delete, new one won't be able to overwrite its remains, taking some of its chunks in since it'll go to a different folder.

the remaining one could be scheduled to be deleted on next minecraft launch, and if it still fails then, reschedule for next and keep doing it until successful. one pc reset later the folder will be finally freed and will delete normally.

still happens in 28a. it doesn't happen often, but from time to time you can still see things out of order if they're on the positive end of x or z axis.

apparently it's mostly transparent things like water, slime blocks and such.

attached screenshot

can reproduce in 28a. create a portal with end frames, then break the middle parts.

wrong particles are still present.

with 1.8's barrier blocks going over walls shouldn't be a problem anymore though.

i know, hence my response.

a "missing texture" error message displayed in any game is definitely not something that's intended, that's why i still say this wasn't fixed, and most likely won't be until the portal gets a designated texture or has the particles disabled.

the problem with that block was fixed, but using the same command while replacing other blocks still causes problems.

id 63, 68, 90, 144 will be invisible until it lands.

id 51 will fall as a purple/black block, and revert to normal upon landing. same goes for 53, 55, 64, 67, 71, 85, 93, 94, 101, 102, 107, 108, 109, 111, 113, 114, 128, 131, 132, 134, 135, 136, 139, 140, 156, 160, 163, 164, 175.

id 8, 9, 10, 11, 54, 130, 146, will instantly crash minecraft.

so will 65, but it'll be a different crash (upon landing rather than as soon as command's sent).

i'm not sure i'd call this version fixed. now instead of lava particles it has the black and purple squares texture.

still the case in 14w02b.

attached a screenshot that shows the bug still happening in 1.7.2

it wasn't fixed, the status/resolution needs to be changed.

i still see it happening in 1.7.2. the only thing that got fixed was the blinking. before 1.7.2 it was blinking like crazy, now it's just permanently visible.

only part of the lake glitches through the stained glass though, but it's always the exact same part.

http://i.imgur.com/vCBXM7d.png

for the record, my pc is intel i5 3330, geforce gts 450, 8 gb ram, win7 64 bit.

edit: figured it out. the glitch happens when the x/z coordinates cross zero. whenever the coordinate goes from negative to positive, the glitch appears. happens to both x and z coordinates.

http://i.imgur.com/iM2LXXK.png

that castle comes from the "tale of kingdoms" mod, either part 1 or 2.

if you used it at one point, then deleted your world and remade a new one with the same name, it's possible it "imported" some of the chunks that minecraft failed to delete.

the failure to delete existing worlds/saves is a pretty old minecraft bug.

either that or you actually installed the mod into your world which caused this, in which case the ticket's invalid.

the ender chests are tile entities, their inventories just aren't stored in them.

a custom name tag could be saved in the chest's tile entity as it is for regular chests, and then displayed on the gui, changing depending from what ender chest block the player tried to access without even touching the inventory though.

it still seems to happen on 1.5.1. one server i go to uses a lot of command blocks to try replicating an analog clock by using the scoreboard in a specific way to create "wireless redstone", and a few of the command blocks get erased all the time.