Oxidization data map doesn't work without extending vanilla's WeatheringCopper{Variant}Block classes.

[VoidLeech]

Minecraft Version: 1.21.1 (and up)

NeoForge Version: 21.1.143

Logs: n/a

Steps to Reproduce:

1. Create a block using the WeatheringCopperFullBlock constructor (properties don't matter)
2. Add the block to the oxidizables data map
3. Place block
4. Wait
5. Block will not randomtick.

An example of this in the wild is Create.

Description of issue:
Or at the very least the docs are wrong as they state using the vanilla class is enough:
https://docs.neoforged.net/docs/resources/server/datamaps/builtin#neoforgeoxidizables
Whether a block is random ticked is cached at registry freeze. WeatheringCopper{Variant}Block checks the map in WeatheringCopper for this (and does not check the isRandomlyTicking block property (that vanilla also doesn't set) so that's not a workaround), when the data map is obviously not loaded yet and so will not contain our new block. Thus without extending the class and overriding isRandomlyTicking, the block won't be ticked.

[neoforged-releases]

🚀 This issue has been resolved in NeoForge version 21.5.43-beta, as part of #2153.