MC-260750Magma blocks use unnecessary random ticking for an outdated feature, causing performance issues
This is an optimization issue, although it is notable only on very specific cases such as the one described later.
The bug
Prior to 1.13, magma blocks used to extinguish water above them by using the random ticking system. After the update, this feature was removed making the random ticking no longer necessary for magma blocks. However, this feature was not properly removed and some remaining code is still present on the game, more concretely, the random ticking. Due to this, the game still checks for magma blocks on random ticking wasting a bit of performance.
Steps to reproduce
For expected behaviour:
- Create a superflat world just with the bedrock and 20 layers of stone, and with mobs disabled.
- Set 'random tick speed' game rule to an high number (1000+)
On the Alt+F3 menu, notice how performance remains unaffected.
For this bug:
- Create a superflat world just with the bedrock and 20 layers of magma blocks and mobs disabled.
- Set 'random tick speed' game rule to an high number (1000+)
On the Alt+F3 menu, notice how the performance meter shows an increase.
This is very likely not intended, because apparently magma blocks don't do anything related to random events or game ticking (except for entity damage, but that's from a different).
Code analysis
Here's a code analysis along with a potential fix regarding this issue.
The following is based on a decompiled version of Minecraft 1.19.2 using MCP-Reborn.
public class MagmaBlock extends Block { ... public void randomTick(BlockState $bs, ServerLevel $sl, BlockPos $bp, RandomSource $rs) { BlockPos blockpos = $bp.above(); if ($sl.getFluidState($bp).is(FluidTags.WATER)) { $sl.playSound((Player)null, $bp, SoundEvents.FIRE_EXTINGUISH, SoundSource.BLOCKS, 0.5F, 2.6F + ($sl.random.nextFloat() - $sl.random.nextFloat()) * 0.8F); $sl.sendParticles(ParticleTypes.LARGE_SMOKE, (double)blockpos.getX() + 0.5D, (double)blockpos.getY() + 0.25D, (double)blockpos.getZ() + 0.5D, 8, 0.5D, 0.25D, 0.5D, 0.0D); } } ...
If we look at the above class, we can see that the block is checking if a water fluid is in the same block position as the magma block, which is impossible in vanilla minecraft but the game still checks this because it is used on random ticking. Before 1.13, the block used to check the block above instead, for the feature explained before (it is very likely that the old code is now commented). After the update, this was forgotten to be removed and at net.minecraft.world.level.block.Blocks the magma block definition still defines it as a random ticking block.
Potential Fix:
Simply removing the .randomTicks() method within this line of code should resolve this problem, along with removing MagmaBlock.randomTick() method to remove extra unnecessary code:
public class Blocks { ... public static final Block MAGMA_BLOCK = register("magma_block", new MagmaBlock(BlockBehaviour.Properties.of(Material.STONE, MaterialColor.NETHER).requiresCorrectToolForDrops().lightLevel((p_152684_) -> { return 3; }).randomTicks().strength(0.5F).isValidSpawn((p_187421_, p_187422_, p_187423_, p_187424_) -> { return p_187424_.fireImmune(); }).hasPostProcess(Blocks::always).emissiveRendering(Blocks::always))); ... }
Linked Issues
Created Issue:
Magma blocks use random ticking for an outdated feature
This is an optimization issue, altought it is notable only on very specific cases such as the one described later.
The bug
Prior to 1.13, magma blocks used to extingish water above them by using the random ticking system. After the update, this feature was removed making the random ticking no longer necessary for magma blocks. However, this feature was not properly removed and some remaining code is still present on the game, more concretely, the random ticking. Due to this, the game still checks for magma blocks on random ticking wasting a bit of performance.
Steps to reproduce:
For expected behaviour:
- Create a superflat world just with the bedrock and 20 layers of stone, and with mobs disabled.
- Set 'random tick speed' game rule to an high number (1000+)
For this bug:
- Create a superflat world just with the bedrock and 20 layers of magma blocks and mobs disabled.
- Set 'random tick speed' game rule to an high number (1000+)
This is very likely not intended, because apparently magma blocks don't do anything related to random events or game ticking (except for entity damage, but that's from a different).
Code analysis
Here's a code analysis along with a potential fix regarding this issue.
The following is based on a decompiled version of Minecraft 1.19.2 using MCP-Reborn.
net.minecraft.world.level.block.MagmaBlock.javapublic class MagmaBlock extends Block implements Fallable, SimpleWaterloggedBlock { ... public void randomTick(BlockState $bs, ServerLevel $sl, BlockPos $bp, RandomSource $rs) { BlockPos blockpos = $bp.above(); if ($sl.getFluidState($bp).is(FluidTags.WATER)) { $l.destroyBlock(blockpos, true); $sl.playSound((Player)null, $bp, SoundEvents.FIRE_EXTINGUISH, SoundSource.BLOCKS, 0.5F, 2.6F + ($sl.random.nextFloat() - $sl.random.nextFloat()) * 0.8F); $sl.sendParticles(ParticleTypes.LARGE_SMOKE, (double)blockpos.getX() + 0.5D, (double)blockpos.getY() + 0.25D, (double)blockpos.getZ() + 0.5D, 8, 0.5D, 0.25D, 0.5D, 0.0D); } } ...If we look at the above class, we can see that the block is checking if a water fluid is in the same block position as the magma block, which is impossible in vanilla minecraft but the game still checks this because it is used on random ticking. Before 1.13, the block used to check te block above instead, for the feature explained before (it is very likely that the old code is now commented). After the update, this was forgotten to be removed and at net.minecraft.world.level.block.Blocks the magma block definition still defines it as a random ticking block.
Potential Fix:
Simply removing the .randomTicks() method within this line of code should resolve this problem, along with removing MagmaBlock.randomTick() method to remove extra unnecessary code:
net.minecraft.world.level.block.Blocks.javapublic class Blocks { ... public static final Block MAGMA_BLOCK = register("magma_block", new MagmaBlock(BlockBehaviour.Properties.of(Material.STONE, MaterialColor.NETHER).requiresCorrectToolForDrops().lightLevel((p_152684_) -> { return 3; }).randomTicks().strength(0.5F).isValidSpawn((p_187421_, p_187422_, p_187423_, p_187424_) -> { return p_187424_.fireImmune(); }).hasPostProcess(Blocks::always).emissiveRendering(Blocks::always))); ... }
This is an optimization issue, altought it is notable only on very specific cases such as the one described later.
The bug
Prior to 1.13, magma blocks used to extingish water above them by using the random ticking system. After the update, this feature was removed making the random ticking no longer necessary for magma blocks. However, this feature was not properly removed and some remaining code is still present on the game, more concretely, the random ticking. Due to this, the game still checks for magma blocks on random ticking wasting a bit of performance.
Steps to reproduce:
For expected behaviour:
- Create a superflat world just with the bedrock and 20 layers of stone, and with mobs disabled.
- Set 'random tick speed' game rule to an high number (1000+)
For this bug:
- Create a superflat world just with the bedrock and 20 layers of magma blocks and mobs disabled.
- Set 'random tick speed' game rule to an high number (1000+)
This is very likely not intended, because apparently magma blocks don't do anything related to random events or game ticking (except for entity damage, but that's from a different).
Code analysis
Here's a code analysis along with a potential fix regarding this issue.
The following is based on a decompiled version of Minecraft 1.19.2 using MCP-Reborn.
net.minecraft.world.level.block.MagmaBlock.javapublic class MagmaBlock extends BlockimplementsFallable, SimpleWaterloggedBlock { ... public void randomTick(BlockState $bs, ServerLevel $sl, BlockPos $bp, RandomSource $rs) { BlockPos blockpos = $bp.above(); if ($sl.getFluidState($bp).is(FluidTags.WATER)) { $l.destroyBlock(blockpos, true); $sl.playSound((Player)null, $bp, SoundEvents.FIRE_EXTINGUISH, SoundSource.BLOCKS, 0.5F, 2.6F + ($sl.random.nextFloat() - $sl.random.nextFloat()) * 0.8F); $sl.sendParticles(ParticleTypes.LARGE_SMOKE, (double)blockpos.getX() + 0.5D, (double)blockpos.getY() + 0.25D, (double)blockpos.getZ() + 0.5D, 8, 0.5D, 0.25D, 0.5D, 0.0D); } } ...If we look at the above class, we can see that the block is checking if a water fluid is in the same block position as the magma block, which is impossible in vanilla minecraft but the game still checks this because it is used on random ticking. Before 1.13, the block used to check te block above instead, for the feature explained before (it is very likely that the old code is now commented). After the update, this was forgotten to be removed and at net.minecraft.world.level.block.Blocks the magma block definition still defines it as a random ticking block.
Potential Fix:
Simply removing the .randomTicks() method within this line of code should resolve this problem, along with removing MagmaBlock.randomTick() method to remove extra unnecessary code:
net.minecraft.world.level.block.Blocks.javapublic class Blocks { ... public static final Block MAGMA_BLOCK = register("magma_block", new MagmaBlock(BlockBehaviour.Properties.of(Material.STONE, MaterialColor.NETHER).requiresCorrectToolForDrops().lightLevel((p_152684_) -> { return 3; }).randomTicks().strength(0.5F).isValidSpawn((p_187421_, p_187422_, p_187423_, p_187424_) -> { return p_187424_.fireImmune(); }).hasPostProcess(Blocks::always).emissiveRendering(Blocks::always))); ... }This is an optimization issue, altought it is notable only on very specific cases such as the one described later.
The bug
Prior to 1.13, magma blocks used to extingish water above them by using the random ticking system. After the update, this feature was removed making the random ticking no longer necessary for magma blocks. However, this feature was not properly removed and some remaining code is still present on the game, more concretely, the random ticking. Due to this, the game still checks for magma blocks on random ticking wasting a bit of performance.
Steps to reproduce:
For expected behaviour:
- Create a superflat world just with the bedrock and 20 layers of stone, and with mobs disabled.
- Set 'random tick speed' game rule to an high number (1000+)
For this bug:
- Create a superflat world just with the bedrock and 20 layers of magma blocks and mobs disabled.
- Set 'random tick speed' game rule to an high number (1000+)
This is very likely not intended, because apparently magma blocks don't do anything related to random events or game ticking (except for entity damage, but that's from a different).
Code analysis
Here's a code analysis along with a potential fix regarding this issue.
The following is based on a decompiled version of Minecraft 1.19.2 using MCP-Reborn.
net.minecraft.world.level.block.MagmaBlock.javapublic class MagmaBlock extends Block { ... public void randomTick(BlockState $bs, ServerLevel $sl, BlockPos $bp, RandomSource $rs) { BlockPos blockpos = $bp.above(); if ($sl.getFluidState($bp).is(FluidTags.WATER)) { $l.destroyBlock(blockpos, true); $sl.playSound((Player)null, $bp, SoundEvents.FIRE_EXTINGUISH, SoundSource.BLOCKS, 0.5F, 2.6F + ($sl.random.nextFloat() - $sl.random.nextFloat()) * 0.8F); $sl.sendParticles(ParticleTypes.LARGE_SMOKE, (double)blockpos.getX() + 0.5D, (double)blockpos.getY() + 0.25D, (double)blockpos.getZ() + 0.5D, 8, 0.5D, 0.25D, 0.5D, 0.0D); } } ...If we look at the above class, we can see that the block is checking if a water fluid is in the same block position as the magma block, which is impossible in vanilla minecraft but the game still checks this because it is used on random ticking. Before 1.13, the block used to check te block above instead, for the feature explained before (it is very likely that the old code is now commented). After the update, this was forgotten to be removed and at net.minecraft.world.level.block.Blocks the magma block definition still defines it as a random ticking block.
Potential Fix:
Simply removing the .randomTicks() method within this line of code should resolve this problem, along with removing MagmaBlock.randomTick() method to remove extra unnecessary code:
net.minecraft.world.level.block.Blocks.javapublic class Blocks { ... public static final Block MAGMA_BLOCK = register("magma_block", new MagmaBlock(BlockBehaviour.Properties.of(Material.STONE, MaterialColor.NETHER).requiresCorrectToolForDrops().lightLevel((p_152684_) -> { return 3; }).randomTicks().strength(0.5F).isValidSpawn((p_187421_, p_187422_, p_187423_, p_187424_) -> { return p_187424_.fireImmune(); }).hasPostProcess(Blocks::always).emissiveRendering(Blocks::always))); ... }
![[Mod] ampolive](../../../data/avatars/users/18949.svg){kind=small}
Magma blocks use unnecessary random ticking for an outdated feature, causing performance issues
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
This is an optimization issue, altough
tit is notable only on very specific cases such as the one described later.The bug
Prior to 1.13, magma blocks used to extingish water above them by using the random ticking system. After the update, this feature was removed making the random ticking no longer necessary for magma blocks. However, this feature was not properly removed and some remaining code is still present on the game, more concretely, the random ticking. Due to this, the game still checks for magma blocks on random ticking wasting a bit of performance.
Steps to reproduce
:For expected behaviour:
- Create a superflat world just with the bedrock and 20 layers of stone, and with mobs disabled.
- Set 'random tick speed' game rule to an high number (1000+)
For this bug:
- Create a superflat world just with the bedrock and 20 layers of magma blocks and mobs disabled.
- Set 'random tick speed' game rule to an high number (1000+)
This is very likely not intended, because apparently magma blocks don't do anything related to random events or game ticking (except for entity damage, but that's from a different).
Code analysis
Here's a code analysis along with a potential fix regarding this issue.
The following is based on a decompiled version of Minecraft 1.19.2 using MCP-Reborn.
net.minecraft.world.level.block.MagmaBlock.javapublic class MagmaBlock extends Block { ... public void randomTick(BlockState $bs, ServerLevel $sl, BlockPos $bp, RandomSource $rs) { BlockPos blockpos = $bp.above(); if ($sl.getFluidState($bp).is(FluidTags.WATER)) { $l.destroyBlock(blockpos, true); $sl.playSound((Player)null, $bp, SoundEvents.FIRE_EXTINGUISH, SoundSource.BLOCKS, 0.5F, 2.6F + ($sl.random.nextFloat() - $sl.random.nextFloat()) * 0.8F); $sl.sendParticles(ParticleTypes.LARGE_SMOKE, (double)blockpos.getX() + 0.5D, (double)blockpos.getY() + 0.25D, (double)blockpos.getZ() + 0.5D, 8, 0.5D, 0.25D, 0.5D, 0.0D); } } ...If we look at the above class, we can see that the block is checking if a water fluid is in the same block position as the magma block, which is impossible in vanilla minecraft but the game still checks this because it is used on random ticking. Before 1.13, the block used to check te block above instead, for the feature explained before (it is very likely that the old code is now commented). After the update, this was forgotten to be removed and at net.minecraft.world.level.block.Blocks the magma block definition still defines it as a random ticking block.
Potential Fix:
Simply removing the .randomTicks() method within this line of code should resolve this problem, along with removing
MagmaBlock.randomTick() method to remove extra unnecessary code:net.minecraft.world.level.block.Blocks.javapublic class Blocks { ... public static final Block MAGMA_BLOCK = register("magma_block", new MagmaBlock(BlockBehaviour.Properties.of(Material.STONE, MaterialColor.NETHER).requiresCorrectToolForDrops().lightLevel((p_152684_) -> { return 3; }).randomTicks().strength(0.5F).isValidSpawn((p_187421_, p_187422_, p_187423_, p_187424_) -> { return p_187424_.fireImmune(); }).hasPostProcess(Blocks::always).emissiveRendering(Blocks::always))); ... }This is an optimization issue, although it is notable only on very specific cases such as the one described later.
The bug
Prior to 1.13, magma blocks used to extinguish water above them by using the random ticking system. After the update, this feature was removed making the random ticking no longer necessary for magma blocks. However, this feature was not properly removed and some remaining code is still present on the game, more concretely, the random ticking. Due to this, the game still checks for magma blocks on random ticking wasting a bit of performance.
Steps to reproduce
For expected behaviour:
- Create a superflat world just with the bedrock and 20 layers of stone, and with mobs disabled.
- Set 'random tick speed' game rule to an high number (1000+)
For this bug:
- Create a superflat world just with the bedrock and 20 layers of magma blocks and mobs disabled.
- Set 'random tick speed' game rule to an high number (1000+)
This is very likely not intended, because apparently magma blocks don't do anything related to random events or game ticking (except for entity damage, but that's from a different).
Code analysis
Here's a code analysis along with a potential fix regarding this issue.
The following is based on a decompiled version of Minecraft 1.19.2 using MCP-Reborn.
net.minecraft.world.level.block.MagmaBlock.javapublic class MagmaBlock extends Block { ... public void randomTick(BlockState $bs, ServerLevel $sl, BlockPos $bp, RandomSource $rs) { BlockPos blockpos = $bp.above(); if ($sl.getFluidState($bp).is(FluidTags.WATER)) { $l.destroyBlock(blockpos, true); $sl.playSound((Player)null, $bp, SoundEvents.FIRE_EXTINGUISH, SoundSource.BLOCKS, 0.5F, 2.6F + ($sl.random.nextFloat() - $sl.random.nextFloat()) * 0.8F); $sl.sendParticles(ParticleTypes.LARGE_SMOKE, (double)blockpos.getX() + 0.5D, (double)blockpos.getY() + 0.25D, (double)blockpos.getZ() + 0.5D, 8, 0.5D, 0.25D, 0.5D, 0.0D); } } ...If we look at the above class, we can see that the block is checking if a water fluid is in the same block position as the magma block, which is impossible in vanilla minecraft but the game still checks this because it is used on random ticking. Before 1.13, the block used to check the block above instead, for the feature explained before (it is very likely that the old code is now commented). After the update, this was forgotten to be removed and at net.minecraft.world.level.block.Blocks the magma block definition still defines it as a random ticking block.
Potential Fix:
Simply removing the .randomTicks() method within this line of code should resolve this problem, along with removing MagmaBlock.randomTick() method to remove extra unnecessary code:
net.minecraft.world.level.block.Blocks.javapublic class Blocks { ... public static final Block MAGMA_BLOCK = register("magma_block", new MagmaBlock(BlockBehaviour.Properties.of(Material.STONE, MaterialColor.NETHER).requiresCorrectToolForDrops().lightLevel((p_152684_) -> { return 3; }).randomTicks().strength(0.5F).isValidSpawn((p_187421_, p_187422_, p_187423_, p_187424_) -> { return p_187424_.fireImmune(); }).hasPostProcess(Blocks::always).emissiveRendering(Blocks::always))); ... }
![[Mojang] Gegy](../../../data/avatars/users/10122.svg){kind=small}
[Mojang] Gegy[Mojang] GegyThis is an optimization issue, although it is notable only on very specific cases such as the one described later.
The bug
Prior to 1.13, magma blocks used to extinguish water above them by using the random ticking system. After the update, this feature was removed making the random ticking no longer necessary for magma blocks. However, this feature was not properly removed and some remaining code is still present on the game, more concretely, the random ticking. Due to this, the game still checks for magma blocks on random ticking wasting a bit of performance.
Steps to reproduce
For expected behaviour:
- Create a superflat world just with the bedrock and 20 layers of stone, and with mobs disabled.
- Set 'random tick speed' game rule to an high number (1000+)
For this bug:
- Create a superflat world just with the bedrock and 20 layers of magma blocks and mobs disabled.
- Set 'random tick speed' game rule to an high number (1000+)
This is very likely not intended, because apparently magma blocks don't do anything related to random events or game ticking (except for entity damage, but that's from a different).
Code analysis
Here's a code analysis along with a potential fix regarding this issue.
The following is based on a decompiled version of Minecraft 1.19.2 using MCP-Reborn.
net.minecraft.world.level.block.MagmaBlock.javapublic class MagmaBlock extends Block { ... public void randomTick(BlockState $bs, ServerLevel $sl, BlockPos $bp, RandomSource $rs) { BlockPos blockpos = $bp.above(); if ($sl.getFluidState($bp).is(FluidTags.WATER)) {$l.destroyBlock(blockpos,true); $sl.playSound((Player)null, $bp, SoundEvents.FIRE_EXTINGUISH, SoundSource.BLOCKS, 0.5F, 2.6F + ($sl.random.nextFloat() - $sl.random.nextFloat()) * 0.8F); $sl.sendParticles(ParticleTypes.LARGE_SMOKE, (double)blockpos.getX() + 0.5D, (double)blockpos.getY() + 0.25D, (double)blockpos.getZ() + 0.5D, 8, 0.5D, 0.25D, 0.5D, 0.0D); } } ...If we look at the above class, we can see that the block is checking if a water fluid is in the same block position as the magma block, which is impossible in vanilla minecraft but the game still checks this because it is used on random ticking. Before 1.13, the block used to check the block above instead, for the feature explained before (it is very likely that the old code is now commented). After the update, this was forgotten to be removed and at net.minecraft.world.level.block.Blocks the magma block definition still defines it as a random ticking block.
Potential Fix:
Simply removing the .randomTicks() method within this line of code should resolve this problem, along with removing MagmaBlock.randomTick() method to remove extra unnecessary code:
net.minecraft.world.level.block.Blocks.javapublic class Blocks { ... public static final Block MAGMA_BLOCK = register("magma_block", new MagmaBlock(BlockBehaviour.Properties.of(Material.STONE, MaterialColor.NETHER).requiresCorrectToolForDrops().lightLevel((p_152684_) -> { return 3; }).randomTicks().strength(0.5F).isValidSpawn((p_187421_, p_187422_, p_187423_, p_187424_) -> { return p_187424_.fireImmune(); }).hasPostProcess(Blocks::always).emissiveRendering(Blocks::always))); ... }This is an optimization issue, although it is notable only on very specific cases such as the one described later.
The bug
Prior to 1.13, magma blocks used to extinguish water above them by using the random ticking system. After the update, this feature was removed making the random ticking no longer necessary for magma blocks. However, this feature was not properly removed and some remaining code is still present on the game, more concretely, the random ticking. Due to this, the game still checks for magma blocks on random ticking wasting a bit of performance.
Steps to reproduce
For expected behaviour:
- Create a superflat world just with the bedrock and 20 layers of stone, and with mobs disabled.
- Set 'random tick speed' game rule to an high number (1000+)
For this bug:
- Create a superflat world just with the bedrock and 20 layers of magma blocks and mobs disabled.
- Set 'random tick speed' game rule to an high number (1000+)
This is very likely not intended, because apparently magma blocks don't do anything related to random events or game ticking (except for entity damage, but that's from a different).
Code analysis
Here's a code analysis along with a potential fix regarding this issue.
The following is based on a decompiled version of Minecraft 1.19.2 using MCP-Reborn.
net.minecraft.world.level.block.MagmaBlock.javapublic class MagmaBlock extends Block { ... public void randomTick(BlockState $bs, ServerLevel $sl, BlockPos $bp, RandomSource $rs) { BlockPos blockpos = $bp.above(); if ($sl.getFluidState($bp).is(FluidTags.WATER)) { $sl.playSound((Player)null, $bp, SoundEvents.FIRE_EXTINGUISH, SoundSource.BLOCKS, 0.5F, 2.6F + ($sl.random.nextFloat() - $sl.random.nextFloat()) * 0.8F); $sl.sendParticles(ParticleTypes.LARGE_SMOKE, (double)blockpos.getX() + 0.5D, (double)blockpos.getY() + 0.25D, (double)blockpos.getZ() + 0.5D, 8, 0.5D, 0.25D, 0.5D, 0.0D); } } ...If we look at the above class, we can see that the block is checking if a water fluid is in the same block position as the magma block, which is impossible in vanilla minecraft but the game still checks this because it is used on random ticking. Before 1.13, the block used to check the block above instead, for the feature explained before (it is very likely that the old code is now commented). After the update, this was forgotten to be removed and at net.minecraft.world.level.block.Blocks the magma block definition still defines it as a random ticking block.
Potential Fix:
Simply removing the .randomTicks() method within this line of code should resolve this problem, along with removing MagmaBlock.randomTick() method to remove extra unnecessary code:
net.minecraft.world.level.block.Blocks.javapublic class Blocks { ... public static final Block MAGMA_BLOCK = register("magma_block", new MagmaBlock(BlockBehaviour.Properties.of(Material.STONE, MaterialColor.NETHER).requiresCorrectToolForDrops().lightLevel((p_152684_) -> { return 3; }).randomTicks().strength(0.5F).isValidSpawn((p_187421_, p_187422_, p_187423_, p_187424_) -> { return p_187424_.fireImmune(); }).hasPostProcess(Blocks::always).emissiveRendering(Blocks::always))); ... }
Normal![[Mojang] Panda](../../../data/avatars/users/41658.png){kind=small}
[Mojang] Pandarelates to
![[Bot] Piston](../../../data/avatars/users/31202.png){kind=small}
Confirmed.
This is feedback, not a bug.
It's a performance issue, not feedback. This actively uses up server performance while having no effect.
(rant alert) Moesh I'm NOT asking for the outdated feature to be added back, I'm just indicating that said old feature was not removed properly and it is causing performance issues. The magma block is literally checking if there's water AT the same block the magma block is IN! This is nonsense.
Please read the full report and not just the title, please reconsider reopening. I think I will ask Avoma to create a new ticket with better and appropiate title and descriptions.
Thanks for the feedback everyone. This bug was caught in the gray area of our "needs gameplay impact" policy. We have triaged this bug and will look to create a more consistent ruling for bugs that indicate performance impact.
Well, it was clearly stated in the title and description it impacted performance.