The Twilight Forest

The Twilight Forest

155M Downloads

Mushrooms break Forcefields

Closed this issue ยท 2 comments

commented

NeoForge Version

21.4.136

Twilight Forest Version

4.7.3220

Client Log

No response

Crash Report (if applicable)

No response

Steps to Reproduce

  1. go to final castle
  2. plant a mushroom so that its outer sides intersect with a forcefield
  3. grow the mushroom

What You Expected

the mushroom will refuse to grow in that area

What Happened Instead

the forcefield is broken and replaced with the mushroom blocks

Additional Details

this also happens with vanilla end portal frames

Please Read and Confirm The Following

  • I have confirmed this bug can be replicated without the use of Optifine.
  • I have confirmed the details provided in this report are concise as possible and does not contained vague information (ie. Versions are properly recorded, answers to questions are clear).
  • I have confirmed this issue is unique and has not been reported already.
commented

While attempting to reproduce this, Brown Mushrooms do not attempt to intersect with Force Fields, but Red Mushrooms do.

commented

Okay, some testing around, this is a vanilla bug.

Huge Brown Mushrooms don't do this because after a certain height, they will check a radius of 3 blocks for valid placement, ie. Air or Leaves. Since Forcefields are neither, the check fails.

On the other hand, Huge Red Mushrooms seem to have a broken check, causing it to always have a radius of 0. Since the trunk passes the clearance test, it'll go ahead with block placement, and the only check in place after that is for solid blocks. Since Forcefields - and to this extent, End Portal Frames - are not solid, they are replaced.

That being said, as of 1.21.6 (I did not test 1.21.5, too many versions to verify this bug and too many times I have to hear Narrator's loud and ugly voice over and over), this does not appear to happen anymore. I'm not sure if we'll be aiming for a 1.21.4 release, but since Final Castle content isn't a priority, I would say this can be closed, and when a port to a later version happens, this is effectively resolved.