// public static final Block STRIPPED_DARK_OAK_WOOD = register("stripped_dark_oak_wood", new RotatedPillarBlock(BlockBehaviour.Properties.of(Material.WOOD, MaterialColor.COLOR_BROWN).strength(2.0F).sound(SoundType.WOOD)));
public static final Block STRIPPED_MANGROVE_WOOD = register("stripped_mangrove_wood", log(MaterialColor.COLOR_RED, MaterialColor.COLOR_RED));While pulled from forge (for modding) Unless forge completely messed up (possible) The STRIPPED_WOOD for mangrove is using the log() method, while the Normal one uses 'new rotatedpill...'
It's stands out as the only WOOD variant to use the log() method. I have a tendency to think this is in MC itself, as forge tends to effect only 1 of a group of things that should be treated the same.
Frankly I don't know where this issue comes from (forge or Mojang)... so reported to both.
Attachments
Comments 5
Bug reports must have gameplay impact; code analysis results without an actual problem aren't accepted.
Additionally,you're basing your report solely on modded content.
@unknown Please remain civil. @unknown is correct, bug reports are generally only accepted in this bug tracker if they actually contain some sort of gameplay impact. Code inconsistencies that do not result in a direct gameplay impact are usually not tracked as bugs.
So, what I'm being told is that, ' There is no correct place to report this ', or is it the standing that ' the team ' doesn't care about what isn't seen?
Let me be clear. I want to report this PROPERLY.. but find it funny that . Mojang is the first.. and I mean first to actively reject a code report.
Cannot confirm in 1.19, 1.19.2, 1.19.3, or 1.19.4-rc2.