Torches placed by the world generator and are supposed to attach to a block float instead.
How to recreate: Find any torches that are placed by the world generator (Villages, Mineshafts, etc.), and you will see that the torches float when they should be attached to a block.
This is displayed in the development console:
[Server thread/ERROR]: Tried to setBlockAndData(minecraft:torch/0) but it's an invalid state. Defaulting to minecraft:torch[facing=up] instead (minecraft:torch/5)
Related issues
is duplicated by
Attachments
Comments


Well Mojang just realeased a new snapshot so hopefully that will fix the problem.

Nope, this glitch still exsists in 14w27b.

Aw thats a bummer maby you need to just create a new world and see what happens.

I hate to bother you Mojang, but this is a somewhat severe bug that needs to fixed. Can you at least let me know that your working on it?

Probable cause reported in MC-59211. This is displayed in development console:
[Server thread/ERROR]: Tried to setBlockAndData(minecraft:torch/0) but it's an invalid state. Defaulting to minecraft:torch[facing=up] instead (minecraft:torch/5)"

Confirmed in 14w28a. Torches on the black wool/fence posts generated in villages "float" instead of being attached to the block. In the snapshots, this is also observed in the "church" in villages.
FYI torches have been observed sometimes "floating" on black wool [in villages], in mineshafts and strongholds as far back as at least Minecraft 1.4.7.
I wonder if the code noted in MC-59211 could be modified to detect where the solid block is and self-orient generated torches?

ONE QUESTION
Why can't you sum up this report to: All naturally generated torches are placed wrong (Tried to setBlockAndData(minecraft:torch/0) but it's an invalid state. Defaulting to minecraft:torch[facing=up] instead (minecraft:torch/5))
I can already imagine that for example the torches in the mines will get forgotten.
Reports about other torch issues:
MC-53897 (relates)
MC-60061
MC-45395

Marcono1234, I was actually about to leave when I made this report, and I wasn't sure if it was ALL the torches generated were like this.

So can you please change it now, that it contains all the bugs with generated torches? 😉

Marcono1234, I'll check it out and see if that's the case in 14w29b. If it is, I'll post it.

Although, unless there is a good seed for 14w29b, it will be hard because the chunks load REALLY slow.

Looks like the mods have been busy. Marcono1234, your wish has been taken into action. 🙂

Just edited the description to be more specific. Now, please, no more complaining. 🙂

Yes now it is fine, thank you 😉

No, still in villages in 14w29b.
Flatworld "Desert", Seed / Coordinates see screenshot.

Sorry my comment was incorrect, I saw a light with 3 torches connected and thought it was fixed 😞
Sorry for the irritating comment with "Seems to be fixed for villages" but I found now already two villages where some of the lights had correct placed torches

Marcono1234 summed it up well. Floating torches can sometimes be observed in villages, mineshafts and strongholds, pretty much all world gen.
I don't have the best seed to test, but seed 133 has a village at x-360, z360 and a mineshaft if you dig straight down at x-31, z177

I found a village that seems to have good torches in 14w30c. Maybe it's fixed?

Confirmed seems like it is fixed for villages in 14w30c
But still there for end portals, all the torches are facing away from the block

This is still broken for the end exit portal in 14w31a. I didn't check the other locations specified in the description.
Attached is a screen shot.

I think this might be fixed in the 1.8 release. It looks like a problem in the structure generation code still using the old names for Damage values.

The still occurs in 14w32b

14w33a.
(seed: -6589301973742410408 Village is a short walk to your right)

14w34b.

In 14w34d (and b), the torches now drop themselves consistently, which is actually MC-53897, but they're caused by the same issue of the torches being generated in an incorrect orientation.

Will this be fixed in 1.8? To me, this seems too major just to blow over for months. Can someone at least tell me if mojang is working on this? (This comment is with all respect, I just want to know) Thanks.

As it appears that torches now drop when generated improperly, rather than float, and the error message no longer appears in the console, I'm inclined to consider this issue fixed, and suggest those interested follow MC-53897, which covers the torches being dropped rather than placed correctly. We could update this ticket to reflect the current state of the game, but MC-53897 already exists and is older, so I'm more inclined to just keep that one open and update it with any relevant information.

MC-72437...
Still happening in 1.8...

Reconfirmed for 1.8 also.
Nvm the world (and the one Jasper linked) was generated prior to 1.8. MC-53897 is what I'm getting in a 1.8-generated world.

Just came across how this was fixed. Thank you Mojang!

Not fixed for End portals for 1.8.2-pre4
How to reproduce:
/summon EnderDragon ~ ~ ~ {HealF:-1}
Use this in the overworld and go trough the portal and you will find 4 torches (same for end to overworld)

@ Marcono1234
You are actually referring to MC-53897.

I guess they are the same. The game handles them the same way as flowers or every other block which requires any kind of holder. When the game tests if the block is valid and it is not, it just "drops" the item.