[MC-193315] /setblock and /fill resets the instrument block state of note blocks

The bug

As of 1.16, /setblock and /fill completely ignore the instrument property. It instantly applies the instrument that corresponds to the block below the note block.

How to reproduce

Simply stand on a stone block and type /setblock ~ ~ ~ note_block[instrument=bit] in the chat. The instrument will be set to basedrum rather than the value that was specified in the command.

Related issues

relates to

MC-31100 /setblock and /fill do not update the placed block(s) consistently

Attachments

MC-193315.mp4

Comments

migrated 2020-07-02T20:50:35Z

[media]

Avoma 2020-11-23T20:40:43Z

Can confirm in 20w46a.

migrated 2020-11-23T22:58:34Z

/setblock and /fill always reset the block's blockstate, this is also why you can't place flying flowers.

Avoma 2021-01-16T11:13:17Z

Can confirm in 20w51a.

Avoma 2021-02-01T14:37:50Z

Can confirm in 21w03a.

Avoma 2021-02-15T10:13:24Z

Can confirm in 21w06a.

Avoma 2021-02-28T20:06:29Z

Can confirm in 1.16.5.

Avoma 2021-07-28T17:47:58Z

Can confirm in 1.17.1.

ampolive 2021-10-20T18:43:27Z

Can confirm in 21w42a.

ampolive 2021-11-16T23:06:18Z

Can confirm in 1.18 Pre-release 2.

migrated 2022-05-31T12:04:25Z

I don't see how this is any different from MC-31100; additionally, if you re-run the command on an already existing note block, it will stay the same, just like most of the blocks listed in that report.

This should be marked as duplicate, and the instrument state added to the list, rather than related.

muzikbike 2022-11-17T21:52:55Z

Can confirm in 22w46a.

Maartin 2024-10-30T16:36:00Z

This seems to have been resolved in the latest snapshot (24w44a)