Certain blocks do not update when falling, placed or cloned next to a power source
The bug
When certain block entities such as a dropper/dispenser or a command block that contain NBT data for items or a command is either placed manually on a power source or cloned on a power source it will receive power because a repeater gets power from the side of it but the dispenser will not place/drop anything and the command block will not run the command.
How to reproduce
- Place down a dispenser or dropper or command block
- Put items or a command into the block, depending what it is
- Control and middle-click the block to get the block with NBT data
- Place this on a power source such as a redstone torch or a redstone block
→ It should run the command or drop/place something but it does not
Note: this also affects note blocks, they won't play a note until they received a block update.
Test command for falling block, insert into a command block and trigger:
summon falling_block ~ ~2 ~ {
BlockState:{Name:"minecraft:stone"},
Time:1s,
Passengers:
[
{
id:"falling_block",
BlockState:{Name:"minecraft:redstone_block"},
Time:1s,
Passengers:
[
{
id:"falling_block",
BlockState:{Name:"minecraft:command_block"},
TileEntityData:{Command:"say Test"},
Time:1s
}
]
}
]
}
Related issue
MC-31100 when using /setblock to place the block it does not update (and more)
Code analysis
Code analysis by Marcono1234 can be found in this comment on bug report MC-18631.
Linked Issues
is duplicated by13
- Unresolved
Meri Diana
gentlegiantJGC- 20
- 14
- Confirmed
Low
- Platform
- Commands
- /clone block-entity block-update command_block dispenser dropper note_block powered redstone
14w11b - 1.20.2
14w11b 14w17a 14w18a 14w30b 14w30c 1.8 1.8.1-pre3 15w33b 15w33c 15w34a 1.10.2 16w42a 1.12-pre7 1.12 1.12.1-pre1 1.12.1 1.12.2-pre1 1.12.2-pre2 1.12.2 17w43a 17w43b 17w45b 17w46a 17w47a 17w47b 17w48a 18w01a 18w03b 18w05a 18w16a 18w22a 1.13-pre1 1.13-pre2 1.13-pre4 1.13-pre6 1.13-pre7 1.13-pre8 1.13 1.13.1-pre1 1.13.1 1.13.2 18w48a 18w48b 18w49a 19w03b 19w03c 19w04b 19w05a 19w06a 19w07a 19w12b 19w13b 1.14.1 1.14.2-pre2 1.14.2-pre3 1.15.2-pre1 1.15.2 20w06a 20w09a 20w12a 20w13a 20w13b 20w14a 20w17a 20w19a 1.16-pre5 1.16.1 1.16.2-pre3 1.16.4 20w48a 20w49a 20w51a 21w03a 1.16.5 1.17-pre3 1.17.1 1.18.2 1.19.1-pre5 1.20.2
Created Issue:
Blocks with tile entities do not update when placed or cloned next to a power source
When a block with a tile id such as a dropper or a command block that contains nbt data for items or a command is either placed on a power source or cloned on a power source it will receive power because a repeater gets power from the side of it but the dispenser will not place/drop anything and the command block will not run the command
Steps to reproduce
1) Place down a dispenser/command block or other tile entity
2) Put items or a command in the block depending what it is
3) Control and middle click the block to get the block with nbt data
4) Place this on a power source such as a torch or a redstone block
5) It should run the command or drop/place something but it does notEnvironment
It should affect every environment
is duplicated by
is duplicated by
relates to
It should affect every environment
Is this still an issue in the most recent versions (currently that is 1.10.2, or 16w42a) of Minecraft? If so, please update the affected versions and help us keeping this ticket updated from time to time. If you are the owner/reporter of this ticket, you can modify the affected version(s) yourself.
When
a block with a tile idsuch as a dropper or a command block that contains nbtdata for items or a command is either placed on a power source or cloned on a power source it will receive power because a repeater gets power from the side of it but the dispenser will not place/drop anything and the command block will not run the commandSteps to reproduce
1) Place down a dispenser/command block or other tile entity
2) Put items or a command in the block depending what it is
3) Control and middle click the block to get the block with nbt data
4) Place this on a power source such as a torch or a redstone block5) It should run the command or drop/place something but it does notWhen certain block entities such as a dropper/dispenser or a command block that contain NBT data for items or a command is either placed manually on a power source or cloned on a power source it will receive power because a repeater gets power from the side of it but the dispenser will not place/drop anything and the command block will not run the command.
Steps to reproduce
- Place down a dispenser or dropper or command block
- Put items or a command into the block, depending what it is
- Control and middle-click the block to get the block with NBT data
- Place this on a power source such as a redstone torch or a redstone block
- It should run the command or drop/place something but it does not
This also affects note blocks, they won't play a note until they received a block update.
See also:
MC-18631, it also happens if you got certain block entities (e.g. regular/Impulse, blank command block), place that manually next to a power source and insert a command afterwards, as well as
MC-31100 if you setblock certain block entities containing NBT data where they would get powered, as well as
MC-80901as falling block.
Code analysis by Marcono1234 in this comment on bugpost
MC-18631.
When certain block entities such as a dropper/dispenser or a command block that contain NBT data for items or a command is either placed manually on a power source or cloned on a power source it will receive power because a repeater gets power from the side of it but the dispenser will not place/drop anything and the command block will not run the command.
Steps to reproduce
- Place down a dispenser or dropper or command block
- Put items or a command into the block, depending what it is
- Control and middle-click the block to get the block with NBT data
- Place this on a power source such as a redstone torch or a redstone block
- It should run the command or drop/place something but it does not
This also affects note blocks, they won't play a note until they received a block update.
See also:
MC-18631, it also happens if you got certain block entities (e.g. regular/Impulse, blank command block), place that manually next to a power source and insert a command afterwards, as well as
MC-31100 if you setblock certain block entities containing NBT data where they would get powered, as well as
MC-80901as falling block.
Code analysis by Marcono1234 in this comment on bugpost
MC-18631.
Blocks with tile entities do not update when falling, placed or cloned next to a power source
When certain block entities such as a dropper/dispenser or a command block that contain NBT data for items or a command is either placed manually on a power source or cloned on a power source it will receive power because a repeater gets power from the side of it but the dispenser will not place/drop anything and the command block will not run the command.
Steps to reproduce
- Place down a dispenser or dropper or command block
- Put items or a command into the block, depending what it is
- Control and middle-click the block to get the block with NBT data
- Place this on a power source such as a redstone torch or a redstone block
- It should run the command or drop/place something but it does not
This also affects note blocks, they won't play a note until they received a block update.
See also
- MC-31100 When using setblock to place the block it does not updae (and more)
Code analysis by Marcono1234 in this comment on bugpost
MC-18631.
is duplicated by
relates to
relates to
When certain block entities such as a dropper/dispenser or a command block that contain NBT data for items or a command is either placed manually on a power source or cloned on a power source it will receive power because a repeater gets power from the side of it but the dispenser will not place/drop anything and the command block will not run the command.
Steps to reproduce
- Place down a dispenser or dropper or command block
- Put items or a command into the block, depending what it is
- Control and middle-click the block to get the block with NBT data
- Place this on a power source such as a redstone torch or a redstone block
- It should run the command or drop/place something but it does not
This also affects note blocks, they won't play a note until they received a block update.
See also
- MC-31100 When using setblock to place the block it does not update (and more)
Code analysis by Marcono1234 in this comment on bugpost
MC-18631.
When certain block entities such as a dropper/dispenser or a command block that contain NBT data for items or a command is either placed manually on a power source or cloned on a power source it will receive power because a repeater gets power from the side of it but the dispenser will not place/drop anything and the command block will not run the command.
Steps to reproduce
- Place down a dispenser or dropper or command block
- Put items or a command into the block, depending what it is
- Control and middle-click the block to get the block with NBT data
- Place this on a power source such as a redstone torch or a redstone block
- It should run the command or drop/place something but it does not
This also affects note blocks, they won't play a note until they received a block update.See also
- MC-31100 When using setblock to place the block it does not update (and more)
Code analysis by Marcono1234 in this comment on bugpost
MC-18631.The bug
When certain block entities such as a dropper/dispenser or a command block that contain NBT data for items or a command is either placed manually on a power source or cloned on a power source it will receive power because a repeater gets power from the side of it but the dispenser will not place/drop anything and the command block will not run the command.
How to reproduce
- Place down a dispenser or dropper or command block
- Put items or a command into the block, depending what it is
- Control and middle-click the block to get the block with NBT data
- Place this on a power source such as a redstone torch or a redstone block
→ It should run the command or drop/place something but it does notNote: this also affects note blocks, they won't play a note until they received a block update.
Related issue
MC-31100 When using setblock to place the block it does not update (and more)
Code analysis
Code analysis by Marcono1234 can be found in this comment on bugpost
MC-18631.
The bug
When certain block entities such as a dropper/dispenser or a command block that contain NBT data for items or a command is either placed manually on a power source or cloned on a power source it will receive power because a repeater gets power from the side of it but the dispenser will not place/drop anything and the command block will not run the command.
How to reproduce
- Place down a dispenser or dropper or command block
- Put items or a command into the block, depending what it is
- Control and middle-click the block to get the block with NBT data
- Place this on a power source such as a redstone torch or a redstone block
→ It should run the command or drop/place something but it does notNote: this also affects note blocks, they won't play a note until they received a block update.
Related issue
MC-31100
When using setblockto place the block it does not update (and more)Code analysis
Code analysis by Marcono1234 can be found in this comment on bugpo
stMC-18631.The bug
When certain block entities such as a dropper/dispenser or a command block that contain NBT data for items or a command is either placed manually on a power source or cloned on a power source it will receive power because a repeater gets power from the side of it but the dispenser will not place/drop anything and the command block will not run the command.
How to reproduce
- Place down a dispenser or dropper or command block
- Put items or a command into the block, depending what it is
- Control and middle-click the block to get the block with NBT data
- Place this on a power source such as a redstone torch or a redstone block
→ It should run the command or drop/place something but it does notNote: this also affects note blocks, they won't play a note until they received a block update.
Related issue
MC-31100 when using /setblock to place the block it does not update (and more)
Code analysis
Code analysis by Marcono1234 can be found in this comment on bug report
MC-18631.
The bug
When certain block entities such as a dropper/dispenser or a command block that contain NBT data for items or a command is either placed manually on a power source or cloned on a power source it will receive power because a repeater gets power from the side of it but the dispenser will not place/drop anything and the command block will not run the command.
How to reproduce
- Place down a dispenser or dropper or command block
- Put items or a command into the block, depending what it is
- Control and middle-click the block to get the block with NBT data
- Place this on a power source such as a redstone torch or a redstone block
→ It should run the command or drop/place something but it does notNote: this also affects note blocks, they won't play a note until they received a block update.
Test command for falling block, insert into a command block and trigger:
summon falling_block ~ ~2 ~ { BlockState:{Name:"minecraft:stone"}, Time:1s, Passengers: [ { id:"falling_block", BlockState:{Name:"minecraft:redstone_block"}, Time:1s, Passengers: [ { id:"falling_block", BlockState:{Name:"minecraft:command_block"}, TileEntityData:{Command:"say Test"}, Time:1s } ] } ] }Related issue
MC-31100 when using /setblock to place the block it does not update (and more)
Code analysis
Code analysis by Marcono1234 can be found in this comment on bug report
MC-18631.
is duplicated by
is duplicated by
Blocks with tile entities do not update when falling, placed or cloned next to a power sourceCertain blocks do not update when falling, placed or cloned next to a power source
is duplicated by
is duplicated by
Certain block entities, when newly placed next to a power source, won't activate until they receive a block update.
Steps To Reproduce:
1. Place a command block to where it will be powered as soon as it is placed.
2. Type a command into the command block, e.g.: "say test".
> Notice the command block won't output "test" although it's powered.
3. Cause a block update next to the command block.
> Notice the command block now outputs "test".
This also occurs with dispensers, droppers, and note blocks.
See also:
MC-51340, it also happens if you got certain block entities with NBT data (e.g. a command block with an inserted command) and place that manually next to a power source, as well as
MC-31100 if you setblock certain block entities with NBT data where they would get powered, as well as
MC-80901 as falling block.
Code analysis by Marcono1234 in this comment.
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
- sponges
- 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)
- 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 don't 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.
Aha! I see it now. Looks like MC-51340.
Duplicated by:
First of all this whole block placing updating blocks thing is really complicated and confusing with Minecraft. Because of that the provided fix might cause other problems but I hope I got that right and currently it does not cause other problems.
The method setBlockState(BlockPos p_177436_1_, IBlockState p_177436_2_) in the class /Client/src/net/minecraft/world/chunk/Chunk.java (MCP 1.8 names) which is called at some point after a block was placed or destroyed used to call only var15.updateContainingBlockInfo(); however I am unsure what this method actually does...
For TileEntities the onNeighborBlockChange(World worldIn, BlockPos pos, IBlockState state, Block neighborBlock) method must be called to update them. This method is called by the notifyBlockOfStateChange(BlockPos pos, final Block blockIn) method.
The reason why this did not affect basic redstone powered blocks is that they update themselves when the onBlockAdded(World worldIn, BlockPos pos, IBlockState state) is called (and this method is called).
public IBlockState setBlockState(BlockPos p_177436_1_, IBlockState p_177436_2_) { //... if (var8 == p_177436_2_) { return null; } else { //... if (var11.getBlockByExtId(var3, var4 & 15, var5) != var9) { return null; } else { if (var9 instanceof ITileEntityProvider) { var15 = this.func_177424_a(p_177436_1_, Chunk.EnumCreateEntityType.CHECK); if (var15 == null) { var15 = ((ITileEntityProvider)var9).createNewTileEntity(this.worldObj, var9.getMetaFromState(p_177436_2_)); this.worldObj.setTileEntity(p_177436_1_, var15); } if (var15 != null) { // Added the following line worldObj.notifyBlockOfStateChange(var15.getPos(), var15.getBlockType()); var15.updateContainingBlockInfo(); } } } } }
Merging with MC-51340 as it's the same cause.
Merging with MC-51340 as it's the same cause.
Thank you for your report!
We're actually already tracking this issue in MC-51340, so I resolved and linked this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MC-51340, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
MC-51340 only covers block entities, my ticket also covers blocks which is not a block entity, such as composter that is used as an example.
Duplicate of MC-51340.
Thank you for your report!
We're tracking this issue in MC-51340, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're actually already tracking this issue in MC-51340, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote or any additional information to the main ticket it would be appreciated.
Please be sure to use the search feature before creating a ticket to see if the issue has already been reported.
Quick Links:
📓 Bug Tracker Guidelines – 🛠 Community Support – 📧 Mojang Support – ✍️ Feedback and Suggestions – 💬 Mojira Discord
This is still a problem but I feel like it is probably going to be marked as "Works as Intended"
Reopened, thanks.
This behavior is somewhat useful as you can use command blocks as block update detectors
Confirmed for 1.12 pre-7.
Please consider what I wrote here.
I'm more than willing to take over all 4 bugposts or, preferrably, all of them bundled into the oldest one, if the OP regarding that type of problem (
MC-18631) doesn't update it; I would also list all 4 test setups for bug reproduction into that one.Meri if you would like to take over this bug post you are more than welcome to.
I am not sure what the process to go about transferring it is though
Hello there!
If you're fine with it, usually the moderators wouldn't oppose transferring and might do so as soon as they see it, unless there'll be a merge of all bugposts including this one, which anyone else might get assigned to, no idea, up to them.
Whenever someone (like we did now) does any changes to a bugpost, including comments, it seems to get into their update feed, so they will see our comments here eventually and then make a decision
Thank you, have a good day and take care!
Gave ticket to Meri Diana
Confirmed for 1.13pre4.
Confirmed for 1.13-pre6.
Confirmed for 1.13-pre7.
Confirmed for 1.13-pre8.
Confirmed for 1.13.
Confirmed for 1.13.1.
Confirmed for 1.16.4 and most recent snapshot (20w48a).
confirmed for 20w49a
Still an issue in snapshot 20W51A
Still an issue in snapshot 21w03a
Still an issue in 1.17.1.
Also affects items with BlockStateTag when placed, even when that block is not a block entity, see this video.
Since this also affects blocks which are not block entities, such as composters and note blocks, I have updated the title to reflect this.