Samū

@EliteTracker It differs, since the animals are supposed to look at the food they are bred/tamed with. They clearly do so, but their orientation in the boat is not accounted for, causing them to look the wrong direction. It works fine when there is a single animal in the boat. I am sure this is not intended.

This is intentional. It's literally specified in the model:

"rotation": {
  "origin": [ 8, 8, 8 ], 
  "axis": "y", 
  "angle": 45, 
  "rescale": true  // <----------
}

The rescale property tells Minecraft to stretch te texture. If set to false, the texture will not be stretched. This property is set to true deliberately though: setting it to false makes the cross model look weird and thin.

@Hipposgrumm the current implementation of fluid-logging allows for fairly easy lavalogging, but I just don't think lavalogging is logical for glow lichen

Confirmed in 21w03a

Can confirm in 1.16.5 and 21w03a

Does this work in fast render mode?

Probably duplicates MC-189818

Duplicates MC-212117

Can confirm

Signs also work, but not completely (you have to dye them too). Anyway I already reported that: MC-212142

Hm I think this is intentional, all that is supposed to happen is rendering the text on signs and the items on item frames bright. 

Can confirm, but not sure whether this is intended or not.

Agreed it's a feature request but can understand that people see this as a bug - anyway glowstone etc. as items do neither glow so it's more of a feature request.

This is intentional. Mojang specifically mentioned that projectiles do not cause vibrations when thrown while sneaking: https://www.minecraft.net/en-us/article/minecraft-snapshot-20w49a

Two remarks here:

• When throwing a projectile while sneaking, it should cause no vibrations (it's an action the player performs silently when sneaking)

• When a projectile lands it does cause a vibration, because it's the projectile and not the player

I can confirm that throwing does not cause a vibration while sneaking, which is WAI, and I can confirm that a landing projectile does cause a vibration which is also WAI.

Can confirm in 20w51a, 1.16.5-rc1 and 1.16.5

No it's not a duplicate. There is a serious difference between MC-46617 and this issue in that this is a rendering difference between fast and fancy/fabulous render mode (or even with F1 toggled on/off) which wasn't an issue in 1.15.2 yet (I've checked!). MC-46617 is marked as WAI, I assume this rendering issue is not intended because it wasn't an issue in 1.15.2 yet.

In addition, I had looked at the game logs and I've found some log messages that say something like 'cannot find uniform InSize' (out of my head), which only appear when loading the enderman invert shader.

So, please don't mark as a duplicate of MC-46617 or as WAI because I've pointed out that is not the case.

This is not a bug this is a request for getting money back - this is not even supposed to be on the bug tracker at all

Can confirm in 20w48a

I can confirm this issue for 1.16.4, but moreover I can probably confirm it's not a duplicate of MC-610 since this is just an issue in the tree generator. Explanation:

MC-610 is about grass and other vegetation being incorrectly positioned (and hence generating floating), but the tree isn't incorrectly positioned. The tree is supposed to generate on the ground, but grass prevents the tree from generating a layer of log blocks in the grass. This is due to a bug in the dark oak tree generator. A tree generator does several checks to prevent it from replacing any solid block. In all cases it checks whether the block can be replaced when it's one of the following conditions:

• It's an air block

• It's a block of leaves

• It's a block with a plant material (MCP name: TALL_PLANTS) - these include grass, tall grass, ferns, etc.

• It's a water block

Once a tree generator has checked for space it generates the log, checking these conditions for replacing blocks once again. However, the dark oak tree generator only checks air and leaves, and does not generate a trunk in plants or water.

I'm not sure whether this is covered by MC-610 but as far as I understood it isn't. This issue might have been introduced in 1.15 as Mojang divided tree generation into several separate parts (i.e. foliage placers, trunk placers, etc.). I would request this issue being opened again.

MC-121364 is probably related but not duplicated - I'm talking about a wrong location of the sound source, which is actually an issue that can be fixed by Mojang.

See updated issue ticket for code analysis.

For the rest, the problems with directional sounds issued in MC-121364 do not apply to this issue.
(sorry if I didn't include code samples upon creation)