mojira.dev
MC-173834

Glowing damaged iron golem outline shows cracks

When a damaged iron golem is glowing, it's outline looks weird

Related issues

MC-174115 The Iron Golem's cracks are not effected by the Spectral Arrow on it's 3rd stage of cracking. MC-176932 Display error when iron golem has glowing effect MC-199895 Wrong Render with Glowing Damaged Iron Golem MC-205746 Glitched golem MC-206282 when shot with a spectral arrow an Iron Golam sometimes has gaps in the outline. MC-206295 Glowing on Iron golem MC-207523 Partly-damaged Iron Golems have holes in their texture that show up in the Glowing effect MC-207618 Strange Glow Effect visual glitch on Iron Golems on their first Damage Skin Change MC-216613 Iron Golem cracks glow with the Glowing effect MC-220270 Iron Golem cracks are outlined by the glowing effect MC-222841 Glow Texture on damaged Iron Golems not consistent MC-223487 Graphical issue with iron golem damage cracks MC-224027 Iron golems while glowing if they are broken the cool black dots are not visible MC-225652 Iron Golem Dam

Attachments

Comments

migrated
[media][media]
migrated

WAI, Iron Golem's glow is meant to display it's damage stage

migrated

The glowing shouldn't be outlining the cracks, which that itself is not intentional.

migrated

Relates to MC-166850 and MC-167444.

migrated

Confirmed in 20w21a.

migrated

If the iron golem gets no cracks, then the glowing effect looks fine. After cracking twice, the outline of the glowing effect returns to normal.

[media]


(version 1.16.1)

Avoma

Can confirm in 20w51a.

Avoma

Can confirm in 21w06a.

Avoma

Can confirm in 21w07a. Feel free to use the following command to make reproducing this much easier:

/summon minecraft:iron_golem ~ ~ ~ {Health:74f,Glowing:1b,NoAI:1b}
migrated

Appears fixed in 21w10a

migrated

Reintroduced in 21w11a
Affects 21w16a

pine1needle

Why was this report reopened and MC-220270 changed from a clone to a duplicate? As far as I am aware, reports are only reopened if a bug is marked as fixed in a specific version, but wasn't actually fixed in that version. That policy helps keep track of fix versions. This bug was indeed fixed in 21w10a, but it was reintroduced in 21w11a.

Chandler

The difference between this issue and others is that no specific fix was attempted for this issue afaik, and the issue only disappeared for a single-snapshot that wasn't intended as a fix and reappeared immediately afterwards.

pine1needle

Why is an intentional fix attempt necessary for the standard reopening policy to apply? The goal of being able to distinguish between truly fixed versions and falsely "fixed" versions is still just as relevant to accidental fixes as it is to intentional fixes.

Also, MC-220270 was already triaged and MC-173834 is not triaged.

Avoma

Can confirm in 21w17a.

migrated

Appears fixed
Possibly due to resolution of MC-223602

migrated

(Unassigned)

Confirmed

Normal

Rendering

rendering

1.15.2, 20w10a, 20w13b, 20w14a, 20w19a, ..., 21w13a, 21w14a, 21w15a, 21w16a, 21w17a

21w10a, 1.17 Pre-release 2

Retrieved