[MC-168169] Text on signs shows different colors if dyed manually or by command

The bug

Colored text on signs has a different color if set by json in a command (/data or /setblock) and a different color if dyed manually using a dye. If this is intentional design and not a bug, it might be worth to say that the color of text dyed using a dye is often unreadable. Attached is a picture comparing the two cases.

How to reproduce

/setblock ~ ~ ~ oak_sign{Text1:"{\"text\":\"test\",\"color\":\"gray\"}"}

Place a sign, write on it and dye it with gray dye
❌ The text color of the signs is not the same

Linked issues

is duplicated by 1

MC-176574 Colored text from signs are quite darker Resolved

relates to 1

MC-168170 Text on signs does not change shade with the sign texture Open

Attachments

MC-168169.mp4

Comments 9

violine1101 2020-03-29T11:04:38Z

Using dye on signs changes the Color tag of the sign block entity, not the text itself. I imagine that this is probably intended in order to not have the text glow that much, while still providing the option to map makers to use the more vibrant colors

Avoma 2021-01-16T15:30:31Z

Can confirm in 20w51a.

Avoma 2021-02-01T13:52:52Z

Can confirm in 21w03a.

Avoma 2021-02-14T17:42:27Z

Can confirm in 21w06a.

Avoma 2021-03-01T10:08:27Z

Can confirm in 1.16.5 and 21w08b.

Avoma 2022-05-09T17:41:45Z

Can confirm in 1.18.2 and 22w18a.

Avoma 2022-07-20T15:48:20Z

Can confirm in 1.19.

takatalvi 2022-08-03T09:43:15Z

After some thought, I feel like this is not a bug, but rather a feature. However, this would need to be confirmed by the devs who could close this as "works as intended".

user-f2760 2022-08-03T10:53:26Z

Yeah, this is absolutely by design/not a bug, JSON colors don't represent the dye colors, and were used to represent the § color codes, you can even provide #hex color codes.