The bug
Item models completely ignore "shade: false" even though they do not ignore other specifications such as the recently added “light_emission"
How to Reproduce
This bug is easily replicable by holding a Calibrated Sculk Sensor in the player's hand and moving the camera in any direction, the models for this block have two "shade: false" cubes that form the amethyst shard on it
Linked issues
Attachments
Comments 9
yes, long ago this same bug occurred in an older version which apparently was fixed but over time it seems to be back, and although the report you direct me to was marked as "won't fix" it would make sense to fix it this time because when "light_emission" was added the item models ignored it the same way as "shade" but it was fixed in the next snapshot, not fixing this bug limits the creation in resourcepacks
Thank you for your report!
We're tracking this issue as MC-248766, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as Won't Fix, which means this is considered a bug but won't be fixed. The description of that ticket or the comments might explain the rationale. Please do not leave a comment on the linked ticket.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
I concur with original poster's likely intent on revisiting this issue in light of MC-275296. The creation and resolution (fixed) of MC-275296 with the same issue on another parameter show a willingness to improve item rendering, two and a half years after the previous ticket was closed, which also because the developer who fixed it was brand new on the team at the closure of MC-248766, I believe constitute new circumstances for this bug. This bug went previously WAI and got revisited previously, so I would hope this ticket can once again either be considered a clone and updated with details from there, or perhaps in light of MC-275296 being fixed we could at the very least reopen the older ticket with an update on emissivity.
If it were to be moved back to MC-248766, how would one propose it be reopened?
@unknown You could write a comment on that ticket requesting that Mojang have another look at it, with an explanation of your reasoning for this request. Please note that this does not guarantee that Mojang will actually reopen and/or fix the issue though.
I have requested an internal Mojang review for MC-248766, you do not need to leave a comment on the ticket.
Thank you. I will silently follow the issue there for the chance that anything happens.
MC-248766 has been reviewed by Mojang and will remain as "Won't Fix".
This means there are currently no plans to fix or reopen this issue. Please do not leave a comment on the issue.
Thank you turbo.
Would MC-248766 describe your issue?