Unfortunately, this issue still exists in version 1.16.4. It seems like you can send the resource pack to the client twice to fix it, but this does cause it to load twice on clients no matter whether they experience this issue or not, which is very annoying.
Unfortunately, this issue still exists in version 1.16.4. It seems like you can send the resource pack to the client twice to fix it, but this does cause it to load twice on clients no matter whether they experience this issue or not, which is very annoying.