As of Minecraft 14w04a and above, it is no longer possible to use "/setblock" to spawn the technical block "minecraft:lit_redstone_lamp" (formerly Block ID 124) into the world. Instead, the default (inactive) "Redstone Lamp" spawns.
The following versions allowed the spawning of active Redstone Lamps:
13w38c, 13w39a, 13w39b, 13w41a, 13w41b, 13w42a, 13w42b, 13w43a, 1.7, 1.7.1, 1.7.2, 13w47e, 13w48b, 13w49a, 1.7.3, 1.7.4, 14w02c, and 14w03b.
The syntax used is:
"/setblock ~ ~2 ~ minecraft:lit_redstone_lamp 0 replace"
Intended behavior:
The Active Redstone Lamp should spawn into the world using the "/setblock" command, and then become an "inactive" Redstone Lamp, provided the Command is not repeatedly executed via a Redstone Clock.
Additional notes:
It is still possible to use the "FallingSand" TileID of 124 to replicate the above intended effect, as in the following syntax:
"/summon FallingSand ~ ~2.5 ~ {TileID:124,Time:1000,TileEntityData:{}}"
Alternately you can also use this syntax, and the block will become intangible:
"/summon FallingSand ~ ~2.5 ~ {TileID:124,Motion:[0.0,0.04,0.0]}"
The following YouTube video shows both the intended behavior, as well as the bug in action:
http://www.youtube.com/watch?v=Wns5BFO-wGA
Also included are a screenshot of the "Active Redstone Lamp" working, in 1.7.4, as well as a screenshot of it no longer working in the 14w05a snapshot.
Linked issues
is duplicated by 1
relates to 1
Attachments
Comments 15
I really hope that's not the case. I know they needed to prevent players from having technical blocks in their inventory, but other technical blocks still spawn into the world, the same as they always have. Case in point, "Block 36" is able to be spawned with "/setblock ~ ~ ~ minecraft:piston_extension", but is no longer a valid block with the "/give" command (because you can't store technical blocks in player inventory, or storage).
I was using Active Redstone Lamps to make "wireless" lighting in my buildings, as well as in one of my current projects, so losing the ability to spawn them is kind of painful.
I find it really weird that the "FallingSand" version of "Block 124" still works perfectly, but the properly named "lit_redstone_lamp" doesn't.
Thank you for responding, and I hope it's just a bug, and will eventually be restored.
Still in 07a
@Kumasasa Yet lit furnaces and redstone ores spawn perfectly with /setblock, so why not the redstone lamp?
Didn't think about that.
still in 08a
Still in 10c
I can confirm what Gary Closse has stated, that this bug still exists in the current snapshot (14w10c). I'm not sure if Dinnerbone, or Grumm, or anyone else is checking on this bug (I doubt it), but it is weird that the Redstone Lamp is the only block in the group that doesn't show its "active" form, with the /setblock command.
Is this still a concern in the current Minecraft version 14w19a / Launcher version 1.3.11 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
Confirmed for 14w19a.
Confirmed for 14w20b.
Confirmed for 14w21b.
You'd think this would be an easy fix.. I'd really like to use this functionality for a mini-map I'm making. I'll up-vote this.
Confirmed for 14w25a and b.
Confirmed for 14w29a.
"Works as intended" ;_;?
I was afraid that would be the case, but, too bad, would have been beautiful, I recall old gorgeous builds with them.
Erik Broes
Looks quite intended since technical blocks are also no longer obtainable bygive