Axolotl inconsistently doesn't show its mouth in-game
Axolotl's mouth texture is inconsistently not shown in-game renders.
Attached image shown red circled-mark.
If you see in-game, you feed them, it never shows open mouth wider. or it has no eye pixel.
Created Issue:
Unused axolotl mouth or neck?
really what is this? what could it be use??
a mouth or a improved neck inside of axolotl's head?
tell me on comment what is this thing on axolotl's texture?
Environment
Axolotl Texture
Axolotl Texture
really what is this? what could it be use??
a mouth or a improved neck inside of axolotl's head?tell me on comment what is this thing on axolotl's texture?
Axolotl's mouth texture is inconsistently not shown in-game renders.
Attached image shown red circled-mark.
If you see in-game, if you feed
Axolotl's mouth texture is inconsistently not shown in-game renders.
Attached image shown red circled-mark.
If you see in-game, if you feed them, it never shows opening mouth wide
Axolotl's mouth texture is inconsistently not shown in-game renders.
Attached image shown red circled-mark.
If you see in-game,
ifyou feed them, it never shows openingmouth wideAxolotl's mouth texture is inconsistently not shown in-game renders.
Attached image shown red circled-mark.
If you see in-game, you feed them, it never shows open mouth wider. or if axolotl has unused face.
Unused axolotl mouth or neck?Axolotl inconsistently mouth not shown in-game
Axolotl's mouth texture is inconsistently not shown in-game renders.
Attached image shown red circled-mark.
If you see in-game, you feed them, it never shows open mouth wider. or i
f axolotl has unused face.Axolotl's mouth texture is inconsistently not shown in-game renders.
Attached image shown red circled-mark.
If you see in-game, you feed them, it never shows open mouth wider. or it has no eye pixel.
Axolotl inconsistentlymouth not shownin-gameAxolotl inconsistently doesn't show its mouth in-game
relates to
relates to
The axolotl texture still has the mouth textures on Bedrock Edition. This isn't in parity with Java Edition since MC-208679 is now fixed in the latest snapshot.
Relates to: MC-176095 MC-199660 MC-208679 MC-250985
May also relate to: MC-159560
The bug
The textures used for the top of the hopper and the side of the hopper contain several regions of unused pixels.
For the hopper's side texture, this follows 23w14a's fixing of MC-203399, which means the side texture is no longer used on the bottom. Therefore, four rectangles of pixels are not used anywhere on the hopper model.
For the hopper's top texture, the ring shape was made thicker in 14w10a (from two pixels to three pixels), which is the version that converted hoppers over to proper block models. However, despite this, the newly added innermost ring of pixels never ended up being used at all, and was not removed even after the Texture Update.
It is therefore possible to remove these four regions from the hopper's side texture, and the innermost ring of pixels from the hopper's top texture, without causing any visual difference to hoppers at all.
How to fix
Fixed versions of the texture files for the sides and top of hoppers are attached to this ticket. Fixing this should be as easy as replacing vanilla's current block/hopper_side.png and block/hopper_top.png textures with these fixed textures.
I've also included Programmer Art versions of these textures, as Programmer Art is also affected by this issue. Programmer Art's fix can be applied in much the same way.
As these assets are modified versions of Mojang's own game assets, intended as a fix to the game, Mojang have all the rights to use these as a fix. If required for some reason, I give Mojang full permission to use these.
Relates to: MC-176095 MC-199660 MC-208679 MC-250985
May also relate to: MC-159560
The bug
The texture files used for the top, side and bottom faces of cauldrons all have unused pixels.
- For the tops of cauldrons, we have a similar situation to MC-262454: in 14w10a, the rim was made three pixels thick, but the cauldron only ever uses the two outermost pixels. The innermost ring is not used by the block at all and therefore can be deleted from the texture entirely without changing how the cauldron looks.
- For the sides of cauldrons, the 8×3 region of pixels at the very bottom center of the cauldron texture are not used at all.
- For the bottom, there are thirty-six pixels that are not used at all, flanking the used space for unknown reasons.
In all three of these cases, these extra pixels were added in snapshot 14w10a, the version in which cauldrons were presumably made to use data-driven block models. However, even at this point in development, the pixels were never actually used, therefore only remaining as an artifact from what is presumably a cauldron model never released to the public. Even the Texture Update did not remove these pixels - if anything, some textures such as the cauldron's side texture appear to be shaded under the assumption that all pixels are used in-game even though they are not. In addition, the Texture Update caused the bottom middle of the cauldron side texture to become filled in with solid color even though it was previously left transparent.
In addition, the "inner" texture for cauldrons contains 48 pixels which, while technically used, are never visible without clipping into the block. As a result, deleting these pixels from the texture will have no effect on the cauldron's appearance in a way that matters. (Since these unused pixels correspond to the bottom texture's used pixels, these two files could even be merged if desired.)
How to fix
Fixed versions of all four texture files for cauldrons are attached to this ticket. Fixing this should be as easy as replacing vanilla's current block/cauldron_top.png, block/cauldron_side.png, block/cauldron_inner and block/cauldron_bottom.png textures with these fixed textures.
I've also included Programmer Art versions of these textures, as Programmer Art is also affected by this issue. Programmer Art's fix can be applied in much the same way.
As these assets are modified versions of Mojang's own game assets, intended as a fix to the game, Mojang have all the rights to use these as a fix. If required for some reason, I give Mojang full permission to use these.
Further notes
The attached "affected areas" image appears to still be missing some unused pixels.
Relates to: MC-176095 MC-199660 MC-208679 MC-250985
May also relate to: MC-159560
The bug
The outermost ring of pixels in the glow item frame texture, as well as the outermost ring of pixels in both the default and Programmer Art versions of the item frame texture, go completely unused by the game and can never be seen under any circumstances.
How to fix
An easy fix - just replace the vanilla item frame and glow item frame texture files with the versions attached, and replace Programmer Art's item frame texture with the fixed Programmer Art item frame texture as well.
Relates to: MC-176095 MC-199660 MC-208679 MC-250985
May also relate to: MC-159560
The bug
In both the vanilla textures and Programmer Art, the two topmost and bottommost rows of pixels in the beacon, as well as the three leftmost and rightmost columns of pixels, go completely unused - only the middle 10×12 rectangle is actually used.
How to fix
An easy fix - just replace the vanilla beacon texture file with the one attached, and replace Programmer Art's with the fixed Programmer Art beacon texture as well.
Relates to: MC-176095 MC-199660 MC-208679 MC-250985
May also relate to: MC-159560
The bug
In both the vanilla textures and Programmer Art, many regions of the brewing stand texture go completely unused. The texture mapping between the default textures and Programmer Art differ as the brewing stand is currently one of only two blocks where the model differs between the two packs, however the same amount of pixels currently go unused.
How to fix
An easy fix - just replace the vanilla brewing stand base texture file with the one attached, and replace Programmer Art's with the fixed Programmer Art brewing stand base texture as well.
I've attached a third texture to this ticket, which is intended for use with MC-262464, as that ticket depends on the repurposing of unused texture regions. If MC-262464 is fixed, then that texture should be used to replace the vanilla texture instead.
Relates to: MC-176095 MC-199660 MC-208679 MC-250985
May also relate to: MC-159560
The bug
The fifth and sixth rows of the tripwire texture go completely unused by the model. The first and second rows are used by unattached tripwire, the third and fourth by attached tripwire and the seventh and eighth by tripwire hooks, but no part of any block model utilizes the fifth or sixth.
How to fix
An easy fix - just replace the vanilla tripwire texture file with the one attached.
Relates to: MC-176095 MC-199660 MC-208679 MC-250985
May also relate to: MC-159560
The bug
In both the vanilla textures and Programmer Art, the four 2×2 regions at each of the corners of the "chorus_flower.png", "chorus_flower_dead.png" and "chorus_plant.png" textures go completely unused by the models.
How to fix
An easy fix - just replace the vanilla "chorus_flower.png", "chorus_flower_dead.png" and "chorus_plant.png" texture files with the versions attached, and replace Programmer Art's "chorus_flower.png", "chorus_flower_dead.png" and "chorus_plant.png" textures with the fixed Programmer Art textures attached as well.
Relates to: MC-176095 MC-199660 MC-208679 MC-250985
May also relate to: MC-159560
The bug
In both the vanilla textures and Programmer Art, large black regions can be found in the texture file "entity/enchanting_table_book.png", covering unused areas of the texture. None of these black regions are actually used in-game and they do nothing other than bloat the texture file size.
How to fix
An easy fix - just replace the vanilla "enchanting_table_book.png" texture file with the version attached, and replace Programmer Art's "enchanting_table_book.png" texture with the fixed Programmer Art texture attached as well.
Further notes
It may also be possible to reduce the dimensions of this texture from 64x32 to 32x32 via simple rearrangement: the page texture at the bottom right could be moved to the bottom left below the other page textures, leaving the rightmost 32x32 region blank and therefore allowing it to be entirely cropped from the texture file. Some simple code changes to make the game point to the page texture's new location would be required, but these would be trivial.
Relates to: MC-176095 MC-199660 MC-208679 MC-250985
May also relate to: MC-159560
The bug
The texture file grass_block_side.png contains several pixels which are completely impossible to see under normal circumstances. While their influence on gameplay is currently nothing more than how they affect mipmapping, their existence may pose a problem in future as is detailed in MC-265667, and it may be advisable to remove these pixels to avert this.
How to fix
Remove all of the green pixels from grass_block_side.png. A fixed version of the file is attached, which removes these pixels. Removing these pixels would also fix MC-262954.
Relates to: MC-176095 MC-199660 MC-208679 MC-250985
May also relate to: MC-159560
The bug
There are large areas of unused pixels in the textures for flowing water and flowing lava.
Water and lava use nonstandard methods of texture mapping, which involve a 32×32 texture rather than a 16×16 textures, which is rotated in increments finer than 90 degrees. There remain areas of the texture which will not be mapped under any known circumstances, and therefore it may be advisable to delete these regions from the texture in the interests of clarity.
How to fix
Very simple: just delete the existing versions of water_flow.png and lava_flow.png from the game's texture files and replace them with the versions attached. The mcmeta files can be left as is.
However, as a resource pack developer, I'd find it preferable if the current method used for flowing textures was scrapped entirely, and there were instead individual 16×16 textures for orthogonal flowing, diagonal flowing, (2,1)-flowing and (1,2)-flowing fluids. This would permit much better customizability and get rid of some weird issues with pixel borders not meeting up as expected.
Relates to: MC-176095 MC-199660 MC-208679 MC-250985
May also relate to: MC-159560
The bug
Much like is the case in MC-266280, the textures for leather armor contain pixels that, while definitely within the region mapped to visible areas, are nonetheless impossible to see under any circumstances due to being obscured by an overlay texture. As such, these overlapped textures can be deleted from the texture file entirely with no visual difference, lowering the file size.
How to fix
An easy fix - just replace the vanilla leather armor texture files with the ones attached, and replace Programmer Art's with the fixed Programmer Art textures as well.
Relates to: MC-176095 MC-199660 MC-208679 MC-250985
May also relate to: MC-159560
The bug
The innermost 4×4 square of pixels in the texture file blocks/piston_inner.png is never possible to see outside of exceptional circumstances such as Spectator mode and debug stick usage. As such, it can be effectively regarded as an unused region of pixels, since in practice it will always be obscured by the piston arm. Deleting these pixels from the texture file (like is done for most other texture files) would make it clearer that these pixels cannot normally be seen.
How to fix
An easy fix - just replace the vanilla piston inner texture file with the one attached, and replace Programmer Art's with the fixed Programmer Art texture as well.
Relates to: MC-176095 MC-199660 MC-208679 MC-250985 MC-271303
May also relate to: MC-159560
The bug
All four textures associated with the lectern block have unused pixels to some degree. There are two types of unused pixels:
- Certain areas of the texture file are not used by the model at all. As a result, deleting them from the texture file does not change how the block looks in any way.
- Certain other areas of the texture are used by the model, however the area in which they are used is obscured by another part of the model (compare MC-268027). As a result, while removing these pixels does change how the block looks, the differences can only be seen by clipping into the block via Spectator mode or other likely unintended means.
Since these pixels are unimportant to the block, removing them will make it clearer to resource pack developers what areas can be ignored when making custom textures, and will likely also decrease file sizes slightly.
- block/lectern_top.png: The top row of pixels and bottom two rows of pixels are completely unused.
- block/lectern_front.png: Some areas are completely unused, and other areas are used in regions blocked by the top element of the lectern, which are therefore never visible.
- block/lectern_sides.png: Some areas are also completely unused, and others in regions also obscured by the topmost element.
- block/lectern_base.png: Most of the central 8×8 region is obscured by the central column, barring two rows which are used by the sides of the bottom plate (MC-268047).
Removing all of these pixels from these four files will make it clear what areas of the texture are used and which can be ignored, all without changing how lecterns look at all (barring the use of Spectator mode and other such means).
How to fix
Fixed versions of all four texture files are attached to this ticket. Fixing this should be as easy as replacing vanilla's current block/lectern_top.png, block/lectern_front.png, block/lectern_sides.png and block/lectern_base.png textures with these fixed textures.
As these assets are modified versions of Mojang's own game assets, intended as a fix to the game, Mojang have all the rights to use these as a fix. If required for some reason, I give Mojang full permission to use these.
Further notes
With the lectern_base.png texture change applied, it may be possible to notice very faint dark stitching around the base - this is the fault of MC-73186, which, while overdue for a fix, ultimately should not be a blocker. Fixing that issue will completely stop any of these black pixels from being visible from the outside.
Relates to: MC-176095 MC-199660 MC-208679 MC-250985 MC-271303
May also relate to: MC-159560
The bug
There is a 2×2 region of pixels in both redstone repeater textures that, under normal circumstances, can never be seen due to always being obscured by a torch element. It can be removed without causing any visual differences (disregarding MC-73186), which should communicate that this area is unused to resource pack creators, and may also reduce the file size.
How to fix
An easy fix - just replace the vanilla block/repeater.png and block/repeater_on.png files with the versions attached, and replace Programmer Art's with the fixed Programmer Art textures as well.
Further notes
As noted in MC-268042 and MC-268057, while this texture change should ideally cause no visual changes, MC-73186's continued existence may cause some incredibly insignificant visual stitching around the bases of each torch. This is a very non-notable side effect, and fixing MC-73186 will get rid of it, meaning that this bug (MC-268056) will cause no visual changes at all upon being fixed.
Relates to: MC-176095 MC-199660 MC-208679 MC-250985 MC-271303
May also relate to: MC-159560
The bug
There are three 2×2 region of pixels in both redstone comparator textures that, under normal circumstances, can never be seen due to always being obscured by torch elements. They can be removed without causing any visual differences (disregarding MC-73186), which should communicate that these areas are unused to resource pack creators, and may also reduce the file size.
How to fix
An easy fix - just replace the vanilla block/comparator.png and block/comparator_on.png files with the versions attached, and replace Programmer Art's with the fixed Programmer Art textures as well.
Further notes
As noted in MC-268042 and MC-268056, while this texture change should ideally cause no visual changes, MC-73186's continued existence may cause some incredibly insignificant visual stitching around the bases of each torch. This is a very non-notable side effect, and fixing MC-73186 will get rid of it, meaning that this bug (MC-268057) will cause no visual changes at all upon being fixed.
Relates to: MC-176095 MC-199660 MC-208679 MC-250985 MC-271303
May also relate to: MC-159560
The bug
Each piglin variant has a total of 48 pixels in the head, about and tusk areas which are completely obscured by other areas of geometry in the head. It is impossible to see any of these pixels from the outside, and they are responsible for a considerable amount of Z-fighting on the inside.
Deleting these pixels from the entities' textures will result in no outward visual differences, reduce Z-fighting from within, decrease the file sizes, and communicate more clearly to resource pack developers that these pixels are in fact not necessary to include in the texture.
How to fix
Fixed versions of all three texture files are attached to this ticket. Fixing this should be as easy as replacing vanilla's current entity/piglin/piglin.png, entity/piglin/piglin_brute.png and entity/piglin/zombified_piglin.png textures with these fixed textures.
As these assets are modified versions of Mojang's own game assets, intended as a fix to the game, Mojang have all the rights to use these as a fix. If required for some reason, I give Mojang full permission to use these.
Relates to: MC-176095 MC-199660 MC-208679 MC-250985 MC-271303
May also relate to: MC-159560
The bug
A 2×2 area of pixels from (7,0) to (8,1) on the hanging mangrove propagule texture does not appear to be used by any stage of the block at all.
How to fix
A fixed version of this texture attached to this ticket. Fixing this should be as easy as replacing vanilla's current block/mangrove_propagule_hanging.png texture with this fixed textures.
As this assets is a modified version of Mojang's own game assets, intended as a fix to the game, Mojang have all the rights to use it as a fix. If required for some reason, I give Mojang full permission to use these.
Relates to: MC-176095 MC-199660 MC-208679 MC-250985
May also relate to: MC-159560
The bug
All three texture files used for nether wart crops contain pixels that cannot normally be seen, by virtue of the fact that the crop model places them too low (MC-250679).
Both the default textures and Programmer Art are affected.
How to fix
Fixed versions of the texture files for nether wart are attached to this ticket. Fixing this should be as easy as replacing vanilla's current block/nether_wart_stage0.png, block/nether_wart_stage1.png and block/nether_wart_stage2.png textures with these fixed textures.
I've also included Programmer Art versions of these textures, as Programmer Art is also affected by this issue. Programmer Art's fix can be applied in much the same way.
As these assets are modified versions of Mojang's own game assets, intended as a fix to the game, Mojang have all the rights to use these as a fix. If required for some reason, I give Mojang full permission to use these.
Unlike the other unused pixel issues I've reported, I've decided to fix this issue by moving everything in the texture up one pixel, as opposed to simply deleting the unused pixels from the texture file.
Relates to: MC-176095 MC-199660 MC-208679 MC-250985 MC-271303
May also relate to: MC-159560
The bug
Both hoglins and zoglins have a total of 68 pixels in the head and tusk areas which are completely obscured by other areas of geometry in the head. It is impossible to see any of these pixels from the outside.
Deleting these pixels from the entities' textures will result in no outward visual differences, decrease the file sizes, and communicate more clearly to resource pack developers that these pixels are in fact not necessary to include in the texture.
In addition, the zoglin texture appears to have eight unused pixels directly to the left of the head area.
How to fix
Fixed versions of all three texture files are attached to this ticket. Fixing this should be as easy as replacing vanilla's current entity/hoglin/hoglin.png and entity/hoglin/zoglin.png textures with these fixed textures.
As these assets are modified versions of Mojang's own game assets, intended as a fix to the game, Mojang have all the rights to use these as a fix. If required for some reason, I give Mojang full permission to use these.
Relates to: MC-176095 MC-199660 MC-208679 MC-250985
May also relate to: MC-159560
The bug
The texture file gui/container/enchanting_table.png contains what appears to be remnants of textures used for an early version of the enchanting UI. In gameplay, these will always be obscured by existing, separate texture files for buttons, rendering the ones baked into enchanting_table.png completely useless. It is therefore possible to delete them from the texture without causing the enchanting table UI to look any different in-game at all, and will considerably decrease the file size.
How to fix
A fixed version of this texture file is attached to this ticket. Fixing this should be as easy as replacing vanilla's current gui/container/enchanting_table.png texture with this fixed texture.
As this assets is amodified version of one of Mojang's own game assets, intended as a fix to the game, Mojang have all the rights to use it as a fix. If required for some reason, I give Mojang full permission to use it.
This fixed version recolors some of the pixels at the left of the three buttons as well, since it appears that the original overlayed button textures bled into this area slightly. I've also fixed MC-229831 with this as well.
Relates to: MC-176095 MC-199660 MC-208679 MC-250985
May also relate to: MC-159560
The bug
Much like the unused buttons mentioned in MC-268376, the anvil's texture contains a massive red rectangle which is always fully obscured by the text field. Deleting this rectangle from the texture file would indicate better that it is an unused feature which is never visible, and doing so would also knock down the file size.
How to fix
Remove these pixels from the texture file. I have two fixed versions of this texture attached - one for the default textures and another for Programmer Art. Fixing this should be as easy as replacing the textures with the versions attached.
Relates to: MC-176095 MC-199660 MC-208679 MC-250985 MC-271303
May also relate to: MC-159560
The bug
The texture files for beds all contain an unused row of black pixels at the very bottom, and an unused column of black pixels at the very right. This affects all colours of bed except red (although in Programmer Art, all 16 colours are affected).
In addition, every bed has 72 pixels which are used by the model, but can never be seen without clipping inside of the bed, corresponding to where the feet meet the bottom of the bed. While removing these does change the way beds look on the inside in Spectator mode and such, it is not a concern at all given the resolution of MC-167243, and they look completely the same from the outside anyway.
How to fix
Remove all these pixels from the texture file. I have attached fixed versions of all texture files to this ticket - it should be as simple as replacing the default textures with these sixteen, and Programmer Art's with the other sixteen (included as a zip as to not exceed the weird 30-file limit).
Relates to: MC-176095 MC-199660 MC-208679 MC-250985 MC-271303
May also relate to: MC-159560
The bug
The four bottom rows of pixels in the sea pickle texture file are not used by any of the sea pickle models at all, and can be removed from the texture file without changing how sea pickles look.
In addition, the bottom pixel of each "filament" used for underwater sea pickles is rendered entirely within the sea pickle model itself. Removing these from the texture also has no effect on the outward appearances of sea pickles (the differences can only be seen via Spectator mode), and therefore these can be removed without affecting anything as well.
How to fix
Remove all these pixels from the texture file. I've attached a fixed version of this texture file to the ticket - all that needs done to resolve this issue is to replace vanilla's version of the sea pickle texture with the version attached.
Discovered while testing the fix to MC-262652.
Relates to: MC-176095 MC-199660 MC-208679 MC-250985 MC-271303
May also relate to: MC-159560
The bug
There are several pixels in the dragon egg texture which go entirely unused by the model. These could be removed from the texture to make it clear what areas resource pack artists should bother texturing, and what areas can be safely ignored.
The leftmost row and rightmost row of the image file are unused, as are the two pixels to the right of the bottom-left pixel and the two to the left of the bottom-right pixel. The top row of pixels, excluding the central four, are also unused.
How to fix
Delete these pixels from dragon_egg.png. A fixed version is attached.

It is the texture which appears between the axolotl's head and the "torso", even though it is very difficult to see in-game, you actually can see it. So I think this is invalid.
ManosSef, i checked and it wasnt there to my suprise!
Iouie E mills, what did you check?
It's not Invalid. I didn't see them inside on this texture, its part of unused parts. check in-game you see them normal face,
its like opening mouth really high, it would be appear to others axolotl color texture.
check the attached image
Can confirm in 21w03a.
It will probably be removed instead of used because that would just look weird.