-
Bug
-
Resolution: Unresolved
-
None
-
Minecraft 13w37b, Minecraft 1.7.9, Minecraft 14w18b, Minecraft 14w20b, Minecraft 1.8.1, Minecraft 1.8.2-pre4, Minecraft 1.8.2-pre6, Minecraft 1.8.7, Minecraft 1.8.9, Minecraft 16w03a, Minecraft 1.10.2, Minecraft 16w43a, Minecraft 1.11.2, Minecraft 1.12 Pre-Release 3, Minecraft 1.12 Pre-Release 5, Minecraft 1.12 Pre-Release 7, Minecraft 1.12, Minecraft 1.12.1 Pre-Release 1, Minecraft 1.12.1, Minecraft 1.12.2 Pre-Release 1, Minecraft 1.12.2 Pre-Release 2, Minecraft 1.12.2, Minecraft 17w43a, Minecraft 17w43b, Minecraft 17w45b, Minecraft 17w46a, Minecraft 17w47a, Minecraft 17w47b, Minecraft 17w48a, Minecraft 17w49a, Minecraft 17w49b, Minecraft 18w01a, Minecraft 18w03b, Minecraft 18w05a, Minecraft 18w10d, Minecraft 18w16a, Minecraft 18w22a, Minecraft 1.13-pre1, Minecraft 1.13-pre2, Minecraft 1.13-pre6, Minecraft 1.13-pre7, Minecraft 1.13-pre8, Minecraft 1.13-pre9, Minecraft 1.13-pre10, Minecraft 1.13, Minecraft 18w30a, Minecraft 18w30b, Minecraft 18w31a, Minecraft 18w32a, Minecraft 18w33a, Minecraft 1.13.1-pre1, Minecraft 1.13.1, Minecraft 1.13.2-pre1, Minecraft 1.13.2-pre2, Minecraft 1.13.2, Minecraft 18w48a, Minecraft 18w48b, Minecraft 18w49a, Minecraft 19w03b, Minecraft 19w03c, Minecraft 19w05a, Minecraft 19w06a, Minecraft 19w07a, Minecraft 19w12b, Minecraft 19w13b, Minecraft 1.14.1, Minecraft 1.14.2 Pre-Release 2, Minecraft 1.14.2 Pre-Release 3, 1.15.2 Pre-Release 1, 1.15.2, 20w06a, 20w13a, 20w13b, 20w14a, 20w17a, 20w19a, 1.16 Pre-release 5, 1.16 Pre-release 6, 1.16 Release Candidate 1, 1.16, 1.16.1, 20w27a, 1.16.2 Pre-release 3, 1.16.2, 1.16.3 Release Candidate 1, 1.16.3, 1.16.4 Pre-release 1, 1.16.4 Pre-release 2, 1.16.4, 20w45a, 20w46a, 20w48a, 20w49a, 20w51a, 21w03a, 1.16.5, 21w05a, 21w05b, 21w06a, 21w15a, 21w16a, 21w17a, 21w18a, 21w19a, 21w20a, 1.17 Pre-release 1, 1.17 Pre-release 3, 1.17 Pre-release 4, 1.17, 1.17.1 Pre-release 1, 1.17.1, 21w37a, 21w41a, 1.18 Pre-release 7, 1.18.2, 22w18a, 1.19 Pre-release 5, 1.19, 1.19.1, 1.19.2, 22w45a, 1.19.3, 23w03a, 23w04a, 23w05a, 23w06a, 23w07a, 1.19.4 Pre-release 3, 1.19.4, 23w13a, 23w14a, 1.20 Pre-release 1, 1.20 Pre-release 2, 1.20 Pre-release 4, 1.20.1, 23w31a, 23w32a, 23w33a, 23w35a, 1.20.2 Pre-release 1, 1.20.2 Pre-release 2, 1.20.2, 23w40a, 23w41a, 23w42a, 23w44a, 1.20.4, 24w03b, 24w04a, 24w05a, 24w11a, 24w12a, 1.20.6, 1.21, 1.21.1, 24w40a, 1.21.2 Pre-Release 1, 1.21.2 Pre-Release 2, 1.21.3
-
- /fill
- /setblock
- banner
- bed
- block-state
- block-update
- button
- cactus
- cake
- carpet
- command_block
- comparator
- crop
- dead_bush
- dispenser
- door
- dropper
- fence_gate
- fern
- flower
- flower_pot
- hopper
- ladder
- lever
- lily_pad
- moving_piston
- mushroom
- nether_portal
- note_block
- piston_head
- pressure-plate
- repeater
- sapling
- sign
- snow
- structure_block
- sugar_cane
- tall_grass
- trapdoor
- tripwire
- tripwire_hook
- vine
-
Confirmed
-
Commands
-
Low
-
Platform
If you setblock certain blocks where they would get powered (e.g. onto redstone torch or redstone block), e.g. with:
/setblock <x> <y> <z> command_block{Command:"say test"}
the command block does not say "test", unless it receives a block update.
This occurs also with e.g. dispensers, droppers, note blocks.
See also:
- MC-51340, it also happens if you got a block entity with NBT data (e.g. a command block with an inserted command) and make it fall, place it or clone it next to a power source, as well as
Code analysis by Marcono1234 in this comment on bugpost MC-18631.
Blocks that do not update when placed with setblock:
( Some of those would be useful for mapmakers to be left not updating, see Note below)
- doors
- dispensers
- droppers
- command blocks
- note blocks
- levers
- fence gates
- beds
- crops
- repeaters
- comparators
- mushrooms
- cake
- carpet
- dead bush
- flowers
- tall grass
- ferns
- flower pots
- pressure plates
- buttons
- hopper
- trapdoors
- ladders
- piston extension
- piston heads
- nether portals
- saplings
- snow layers
- banners
- signs
- structure blocks
- tripwire
- tripwire hooks
- vines
- lily pads
- rails
- redstone lamps
- torches
- coral blocks
Blocks that do update:
- anvils
- sand
- cactus
- dragon eggs
- grass path
- gravel
- concrete powder
- farmland
- fire
- observers
- pistons
- redstone torches (lit state)
- redstone wire (power state and supporting block)
- sponges
- stairs
- sugar cane
- TNT
In short:
- Everything that needs support to exist stays aside from redstone wire, cactus, sugar cane and fire.
- Gravity affected blocks fall.
- Powered/lit/etc state stays the same except for pistons, redstone torches, redstone wire and TNT
- sponges still soak up water
Decorative things like flowers, dead_bush, fern, grass, portals (anything that would naturally require a supporting block) would be in my personal opinion better to be left not updating by usage of commands, so mapmakers can still use it as decorative means for their maps.
Furthermore, when using the /clone-command, the cloned blocks should probably be cloned as-is, so, if you clone blockstated blocks, they should be cloned as that very blockstated block. In order to toggle that, if desired, it could be considered to add another cloneMode for this (see opposing opinion in MC-190526, which was closed as duplicate of this bugpost). A fill-command with intentionally blockstated blocks should not lead to updated blocks as well (unless specified command-wise); the same should also go for e.g. a structure block, as well as worldgen structure.
TLDR: It seems it could be great for mapmakers to be able to toggle blockstate updates, if possible also per-block; this would open up the ability to use blocks such as for example the 159 currently unused (naturally not generated automatically) blockstates giant mushroom blocks as retextured blocks for individual resource packs easily, without the same type of mushroom blocks updating, if placed next to each other also manually and thus have to e.g. alternate the block types, which lowers and complicates the amount of usable blocks.
- is duplicated by
-
MC-49788 Comparators update when power is shut
- Resolved
-
MC-50045 No block updates when deleting a command block with the setblock command
- Resolved
-
MC-63831 Command blocks placed on redstone block using /setblock with 'Command' datatag not activating command on placement
- Resolved
-
MC-64402 Redstone blocks placed using /setblock not firing dispensers
- Resolved
-
MC-68879 Sponges created with /setblock don't absorb water
- Resolved
-
MC-69594 Using /setblock to delete tile-entity block fails and succeeds at the same time
- Resolved
-
MC-75426 Redstone mechanisms only update when the block ID is changed
- Resolved
-
MC-76983 Setblocking a daylight sensor to air doesn't update redstone next to it
- Resolved
-
MC-77180 Setblock lever does not update all blocks
- Resolved
-
MC-95692 Junction Rails
- Resolved
-
MC-117092 Structure Blocks in load mode don't load when activated by a redstone source placed via /setblock or /fill
- Resolved
-
MC-124303 Certain blocks do not update blockstates when placed via command
- Resolved
-
MC-124495 Redstone signals don't update when caused by command
- Resolved
-
MC-127001 /setblock ~ ~ ~ (colour)_coral Sets a land Coral Block
- Resolved
-
MC-132561 The collision box with /setblock vines (damage 0)
- Resolved
-
MC-144634 When using /fill command with torches they can be stacked
- Resolved
-
MC-150051 note blocks not matching block underneath after cloning them
- Resolved
-
MC-154061 Fill command strange behaviour
- Resolved
-
MC-160516 Noteblocks playing harp when filled or setblock
- Resolved
-
MC-190526 /clone doesn't update cloned blocks
- Resolved
-
MC-190599 THE COMMAND /setblock ~ ~ ~ minecraft:grass_block[snowy=true] destroy
- Resolved
-
MC-207084 Floating Grass/Deadbush/Other non solid plants
- Resolved
-
MC-209990 /setblock or /fill does not allow block updates
- Resolved
-
MC-225701 /setblock does not update buttons
- Resolved
-
MC-234077 Incomplete fill of fill command
- Resolved
-
MC-259438 Big dripleaf - not correct model place
- Resolved
-
MC-277277 Placing an observer with "/setblock" or "/fill" will cause it to activate
- Resolved
-
MC-277278 Placing a powered observer with a command only works on the second try
- Resolved
- relates to
-
MC-120790 Redstone lamps and wire update whether they are lit or not when setblocked, but no other blocks do
- Resolved
-
MC-212766 Suspended gravity-affected blocks fall if they recieve an update from the sides or above
- Open
-
MC-51340 Certain blocks do not update when falling, placed or cloned next to a power source
- Reopened
-
MC-57507 Items don't smelt when summoning furnaces with smeltable items and fuel already inside them
- Reopened
-
MC-120682 Redstone power supplying blocks do not update all affected blocks when placed using commands
- Reopened
-
MC-61475 Using /setblock to set block entities with items in their inventory does not update comparators adjacent to the block entity
- Resolved
-
MC-117022 /fill does not always send block updates
- Resolved
-
MC-135288 When use fill command, block does not update
- Resolved
-
MC-171308 Soul fire cannot activate nether portals via setblock command
- Resolved
-
MC-193315 /setblock and /fill resets the instrument block state of note blocks
- Resolved
-
MC-216707 Pointed dripstone does not shatter in mid-air when placed by a command
- Resolved
-
MCPE-177523 Fill command with repeaters (replacing other repeaters) is not working properly.
- Resolved