Blocks drawn incorrectly in crafting grid over NEI recipe ghost #16209
Labels
Status: Triage
Tasks awaiting triage. Removed once a dev confirms the issue as valid.
Type: bugMinor
Your GTNH Discord Username
No response
Your Pack Version
2.6.0
Your Server
SP
Java Version
Java 21
Type of Server
Single Player
Your Expectation
Some blocks - at least the vanilla Chest, and Tinker's Stencil Table, Part Builder, and Tool Station - are drawn incorrectly when put in the slot of a ghost recipe ingredient. (By "ghost recipe", I mean the visual reminder you summon by clicking '?' on a recipe in NEI.)
While the new, real item is totally in front of the fake ghost item, the new real item loses its ability to sort its component graphics correctly. They may even be in reverse order.
The Reality
Repro steps
Have a normal Minecraft Chest in your inventory. Access a normal Minecraft Crafting Table.
Search for 'hopper'. Click the first result to display the recipe. Click the '?' button.
(Note that, for some reason, the existing "ghost" Chest isn't translucent like it should be. That seems like a separate bug.)
Other notes
Arch Linux. Launched through Prism Launcher, running in Flatpak with Prism's included Java 21.0.2 on amd64. OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.0.6. Using an RX 6800 XT (Navi 21).
edit: Also, I'm using these Resource Packs, in this order:
Yes, Angelica is in use, as is default for 2.6.0.
Hopefully this bug is easy to reproduce, and isn't system-specific.
You don't seem to need a Chest or multipart cube item in the ghost recipe for this problem to occur. e.g. using a Stencil Table on the Hopper Cart recipe, this still happens:
..but not if the Stencil Table is on an empty square, not a ghost square:
Your Proposal
Ensure that, when a real Chest-like item made of multiple layers is rendered in a crafting grid square, and a ghost item is rendered underneath, the real Chest-like item does not lose the ability to draw its layers in the correct order.
Final Checklist
The text was updated successfully, but these errors were encountered: