abc55

If you have the pack enabled and you see this, you need to disable the pack

Regarding the font, i recommend using a free font such as Roboto (which is under Appache License), or other fonts from https://fonts.google.com/ (always check the license, some licenses require you to use the same licene for everything you add to it). If you are using a font under Appache License, don't forget to include a copy of the license in the addon as the license requires that.

It seems that this is fixed in 1.10

For anyone who used my shader pack, you need to remove the shader pack after updating. Otherwise, this will happen:

Minecraft supports C style comments in JSON (both /**/ and //). It's perfectly reasonable to have comments in a data format like JSON, especially when it is used to define some behavior. There are some comments in the vanilla entities. If comments are supported in other places, why should they not be supported in arrays? Moreover, comments in an array of objects sometimes work! This really seems like an error in the parsing logic, even the error message indicates that - it reports an error at the end of the array (the ] character), but if it didn't support comments the error would be that // is invalid token. It seems like the comment is parsed successfully, but the parser is left in wrong state after the comment so it doesn't accept some tokens that should be valid.

TL; DR i think this is a bug and minecraft should support comments in arrays

BTW the arrow is reflected from invulnreable entities and can be picked up if it hits the ground

An easier way to reproduce it is to use a player in creative or any player when the pvp gamerule is disabled. This can be exploited to get free effects in survival (disabling pvp is not a cheat)

Sorry, i don't speak your language. You can ask me in english or czech.

This problem is not caused by any resource pack. It's a bug in the rendering code.
The rendering code passes wrong texture coordinates (half of the correct value) to shaders on some devices. Multiplying all coordinates by two in shaders makes it render correctly, which is what this pack does:

If the pack doesn't make it render correctly, please tell us and share the details: how does the pack change the rendering (if the pack doesn't change anything, you almost certainly didn't apply it correctly).

@José Victor Brito de Jesus
Has it ever worked for you? Does applying the pack change something? Did you add it to global resources?

This is probably caused by a mistake in animation controller:

"controller.animation.mooshroom.baby": {
      "states": {
        "baby": { // should be "default"
          "parameters": [ "query.is_baby" ],
          "animations": [
            {
              "baby_transform": [
                {
                  "0.0": 0.0,
                  "1.0": 1.0
                }
              ]
            }
          ]
        }
      }
    },

This pack should allow you to play.

It's only a workaround, not a real fix!

DO NOT USE THIS PACK IF YOU DON'T HAVE THIS BUG!

The workaround has to be applied to each shader separately and i might have missed something, do not expect it to be perfect!

Multiplying all texture coordinates by 2 in the shaders (PSInput.uv *= 2) fixes the problem.

This also applies to other commands which display entity name, for example /testfor