The Bug:
Entities' shaders are applied when beginning to spectate them in third person.
It's important to note that if you were to spectate an entity while in first person, the given entity's shader would be applied. While this is fine and is working as expected, if you were to switch into third person here and then, the shader would be removed therefore leading me to believe that there's some kind of issue here since beginning to spectate entities in third person applies the given entity's shader.
Steps to Reproduce:
Summon a creeper by using the command provided below.
/summon minecraft:creeper ~ ~ ~ {NoAI:1b}Switch into spectator mode and then switch into third person.
Spectate the creeper by left-clicking on it and then observe your surroundings
Take note as to whether or not entities' shaders are applied when beginning to spectate them in third person.
Observed Behavior:
Entities' shaders are applied.
Expected Behavior:
Entities' shaders would not be applied.
Linked issues
is duplicated by 1
Attachments
Comments 21
Is this still a concern in the current Minecraft version 14w30c or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
Is this still an issue in the latest snapshot 16w44a? If so please update the affected versions.
This is an automated comment on any open or reopened issue with out-of-date affected versions.
This bug report is still unresolved after 7 years, and I no longer wish to receive email notifications about it. I cannot find any email settings on my profile, nor is there a "Contact Us" or "Support" link anywhere on the site that I can find. Could anyone offer any help? Thanks.
As the reporter, you always get e-mails when the issue is updated. As far as I know, you would have to ask a mod to remove your ownership of the report to stop receiving e-mails.
Do you know how I can contact a moderator directly? I can't see any messaging feature on my profile or anyone else's.
I've removed your ownership from this ticket. As of now, the ticket is set to 'no user' meaning that if anyone else wants to take ownership of this report you can leave a comment 🙂
Is this still a concern in the current Minecraft version 14w11b or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. - bot