Snow golems aren't protected by fire resistance effect when in hot biomes.
When I spawned a snow golem in the nether and throw a fire resistance potion, it still gets damage! And when it dies it glitches!
Linked Issues
Created Issue:
Snow golems aren't protected by fire resistance effect when in hot biomes.
When I spawned a snow golem in the nether and throw a fire resistance potion, it still gets damage! And when it dies it glitches!
is duplicated by
Affects 1.0.4.1.
is duplicated by
is duplicated by
I can reproduce this on 1.1.4. My device is Windows 10 Home.
I can reproduce this on 1.1.4. My device is Windows 10 Home.
is cloned by
Thank you for your report!
However, this issue has been closed as a Duplicate of MCPE-10657.
It has been linked to this report. If you have additional information, please add it to that report.
If you have not, please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki
Snowgolems always die in the nether and other hot biomes, even when they have the fire resistance effect applied to them. This was fixed at one point as you can see in MCPE-10657, but since that report is so old i was directed to make a new one(:
How to reproduce
1. Summon a snowgolem in the nether, desert, or other hot biome.
2. Immediately apply the fire resistance effect to them, either with potions or commands.
3. The golem will still die ;-;
Expected result
The golem should survive for as long as it has fire resistance.

Confirmed on Samsung Galaxy Note 5. Android 5.1.1 Version: 0.13.0 Build 5
I don't know about the glitching part but you get fire damage technically even with fire resistance potion but the snow golem doesn't catch on "fire".
Does this bug still appear in 0.14.3?, if so, please respond.
Affects 0.15.0 build 3
Affects 0.15.0. (Tested on Windows 10.)
Please respond and add the current version if you can reproduce this issue.
Confirmed for 0.15.4. (Tested on Windows 10.)
Please reply and update affected versions if you're still able to reproduce this issue.
Affects 1.1.0.4.
Fixed in the 1.6.0.1 beta.
This affects 1.16.10, reopen?
Create a new ticket.