The Bug:
Boss bars with the notched style are rendered incorrectly if more than one boss bar is active.
Steps to Reproduce:
Create two boss bars with the notched style.
/bossbar add test1 "Test1"
/bossbar add test2 "Test2"
/bossbar set test1 players @a
/bossbar set test2 players @a
/bossbar set test1 style notched_10
/bossbar set test2 style notched_10
Look at the bottom boss bar.
Take note as to whether or not boss bars with the notched style are rendered incorrectly if more than one boss bar is active.
Observed Behavior:
Boss bars with the notched style are rendered incorrectly if more than one boss bar is active.
Expected Behavior:
Boss bars with the notched style would not be rendered incorrectly if more than one boss bar is active.
Linked issues
is duplicated by
relates to
Attachments
Comments

I can additionally confirm this bug's existence

Confirmed for 1.15.2 and 20w09a

Confirmed for 20w11a

Confirmed for 20w12a

Confirmed for 20w13a

affects 20w14a

Confirmed for 20w16a
Can we get a higher Mojang priority? This is getting kinda ridiculous and pardon me if I'm overestimating the talented legends over at Mojang but this seems like a relatively easy fix.

Confirmed for 20w17a

20w19a
Will it be fixed, because its anoying
Who knows? Mojang Studios decides what will be fixed and when. The most you can do is vote for the issue and pay attention to it until it is.
Confirmed for 1.16.1, as well.

Here's a fix: https://github.com/Leo40Git/MultiBossBarFix
Please note that my fix is probably a sub-optimal way to do it (I basically enable blending, render the boss bar, and disable blending for every boss bar).
Can confirm in 20w51a.
Can confirm in 21w03a.
Can confirm in 21w06a.
Can confirm in 1.17.1. I'm willing to take ownership of this ticket since the current reporter's account has been deactivated.
It seems that the semi-transparent parts of the notch textures become solid black when not at the top position, doesn't sound like it's something hard to fix, but it can be very deceptive.

Affects 1.18.1

Affects 1.18.2
Bug still present in Release 1.15.1