Copper golems do not oxidize

Copper Golem’s entity data “next_weather_age" will not change over time.Here’s some output:

09:17:30.360
[System] [CHAT] Copper Golem has the following entity data: 563947L

09:17:48.093
[System] [CHAT] Copper Golem has the following entity data: 563947L

09:17:53.601
[System] [CHAT] Copper Golem has the following entity data: 563947L

I also found the Lightning Bolt will not change this data too,so Copper Golem will not be affected by Lightning Bolt(except the damage of fire).

Cannot reproduce for me. The oxidation of Copper Golems is based on the gametime rather than random tick, so it usually takes longer than the oxidation of copper chests. To verify this:

1. For example, my Copper Golem had a next_weather_age of 6790970L.

2. /tick freeze

3. /time set 6790968t

4. /tick step 1t And the Copper Golem didn't oxidize because current gametime (6790969) was still less than 6790970.

5. /tick step 1t again. This time you will see the Copper Golem did oxidize.

6. /time query gametime = 6790970

Edit: /time query gametime does not include skipped gameticks. Exactly, gametime should be /time query day * 24000 + /time query daytime.

Information: In Minecraft Wiki, the internal gametime is also known as the daylight cycle time, which means that Copper Golems will not oxidize if the doDaylightCycle game rule is set to false. However, that’s another issue.

So much time? That’s 4 real days… That’s crazy…

Probably intentional, per CaN2crow987’s comment. Tested in snapshot 25w35a.