Topher Donovan

Attached a screenshot of the error in a forest biome.

Seed: 2141519423403999074

To be clear, the resolution is to open the world in the latest version, today it's 1.15.2

disregarding my comments from before, I wonder how fixing this bug would speed up some redstone contraptions?? hmmm....

Still an issue. It last worked in release 1.4.7, Has been broken since 1.5.0.

But it's nearly been three years, so what's the point of fixing it? Everyone's already gotten used to this particular redstone mechanic, so fixing it would probably create even more tickets

Sorry, For some reason, I didn't see the updates in my email. I just tested it and it is still present in 1.8.1-pre3, but since the rest of the redstone community isn't complaining about it, perhaps it just isn't something that's supposed to be fixed.

If you drop the render distance to 16 chunks or fewer, the glitch goes away.

You really have to load the game up and experience it in video mode to experience the trip.

Still present in 12w28b. Kill doesn't respect Damage in Json

/kill @e[type=Item] {Item:{id:minecraft:wool,Damage:14s}}

Still kills ALL wool, not just Damage 14s (red)

This appears to be fixed in 12w28b!

Same thing happened to me today on 14w28a. Doesn't matter where I place a ladder, new ladders crash the game

Time: 7/10/14 7:28 AM
Description: Unexpected error

java.lang.IllegalArgumentException: Cannot get property bck{name=facing, clazz=class ei, values=[north, south, west, east]} as it does not exist!
at bbw.b(SourceFile:91)
at avi.a(SourceFile:47)
at avi.a(SourceFile:35)
at apm.a(SourceFile:2320)
at ait.a(SourceFile:106)
at cdt.a(SourceFile:295)
at bqi.ar(SourceFile:1325)
at bqi.q(SourceFile:1682)
at bqi.ap(SourceFile:863)
at bqi.a(SourceFile:303)
at net.minecraft.client.main.Main.main(SourceFile:120)

Still not working in 14w26c

I can confirm that this is a problem. I am building a CTM map, and I'm trying to test for dropped items. I want to omit the count, because I want to detect all dropped items, not just a dropped item of specific size:

I tried with Red Wool:
/testfor @e[type=Item] {Item:{id:minecraft:wool,Damage:14s}} (Doesn't work)
/testfor @e[type=Item] {Item:{id:minecraft:wool,Damage:14s,Count:1b}} (Doesn't work)

I tried with Andesite stone: (Doesn't Work)
/testfor @e[type=Item] {Item:{id:minecraft:stone,Damage:6s}}

But it does work with TestForBlock, for instance: Red Wool in Slot 0 of a Hopper: (DOES WORK!)
/testforblock -10 101 -4 hopper 0 {Items:[0:{id:minecraft:wool,Slot:0b,Count:3b,Damage:14s}]}

There is definitely something wrong with Damage value in /testfor

Please Close this

Ok, I just barely found one, but it was on like the 30th level I created. I wonder if the bug that chests aren't spawning is affecting how they look when they spawn. I guess this is a duplicate.

I fixed this on windows by doing the following:

1. Uninstall all versions of java (ccleaner helps with this)
2. Go to java.com, click Free Java Download
3. Click on the "See all java downloads" link
4. download and install the Windows Offline 64bit version (if you have 64 bit windows, If your windows is only 32 bit, download the other)

Once Java is updated to the latest and greatest version, You have to integrate Twitch with your minecraft account

1. Log into Mojang.com
2. Click on your account at the top and choose settings.
3. Next to Twitch, click the link and enter your password at twitch.tv
4. Click the Authorize link to authorize your account with Mojang
5. Restart minecraft.

I had this very error until I did these steps.

After a quick search, it appears my issue is captured in https://mojang.atlassian.net/browse/MC-31622

Just to be clear here, In my 13w41b, the render distance slider can be set to 16 chunks, but in the actual game, the terrain is only rendered out 8 chunks. I even switched back to 1.6.3 with Render Distance: Far to check and it renders farther out than 13w41b

Attached.

I'm using 13w41b with Java 1.7.0_40 64bit and it's still only rendering out 8 chunks.

Yes, the error is still present in 1.5

Dear Dico Karssiens, This is NOT a pre-existing bug and I can prove it.

http://www.youtube.com/watch?v=Jk1rp8FmJN8

This video illustrates the difference between the redstone getting cut in 1.4.7 and the pre-releases of 13w0x. Something has indeed changed and it has to be looked at. I'm sure that this is not the only use case where powered redstone getting cut needs to be consistent.

Also, if you watch the video, there is NO repeater in this setup. it's very simple.