-
Bug
-
Resolution: Invalid
-
None
-
1.20.6
-
Plausible
-
Resource Packs
There is no dedicated folder for the two 'beam' textures beacon_beam.png and end_gateway_beam.png. This is unusual when compared to other entities that have multiple textures, where both are stored together in their own sub folder for organization and clarity to help resource pack artists.
Steps to Reproduce:
- Go to the following file path:
C:\Users[user]\AppData\Roaming\.minecraft\versions[latest_version] - Right click the [version].jar] file, and open it in a file explorer (like 7zip or winrar)
- Go to the following path inside the jar:
assets\minecraft\textures\entity
Notes:
guardian_beam.png has not been included in this issue because of MC-271362, where it would be better suited to be placed with the other guardian textures.
- relates to
-
MC-199607 spider_eyes.png is not in the spider folder
- Open
-
MC-199609 There is no dedicated phantom folder in assets/minecraft/textures/entity
- Open
-
MC-200944 Block cracking textures are in the block textures folder, despite not being block textures
- Open
-
MC-200946 Item frame texture/models are in the blocks folders, despite item frames not being a block
- Open
-
MC-212656 Lava and water textures/models are in the blocks folder, despite not being blocks
- Open
-
MC-212659 The Overworld's world files do not have their own subfolder
- Open
-
MC-271359 There is no dedicated location for the two trident textures in assets\minecraft\textures\entity
- Resolved
-
MC-271366 Banner textures are not located in an optimal or intuative file path for resource pack creators
- Resolved
-
MC-271377 There is no dedicated folder for the armadillo.png texture in 'assets/minecraft/textures/entity'
- Resolved
-
MC-271362 There is no dedicated folder for the three guardian related textures in assets/minecraft/textures/entity
- Resolved
-
MC-271365 The two vex textures are located in `textures\entity\illager` instead of their own sub-folder
- Resolved