Immersive Portals (for Forge)

Immersive Portals (for Forge)

3M Downloads

When using dimension stack and having a void above the overworld, all structures will generate floating in that void.

spinosaurus1915 opened this issue ยท 3 comments

commented

According to your testing, does the issue occur with ONLY Immersive Portals mod installed?

Yes

Forge Version

47.4.0

ImmersivePortals Version

3.0.6-mc1.20.1

Latest Log

https://gist.github.com/spinosaurus1915/b8351655372d1ad1b2a6432a5b92e4b6

Crash Report (if applicable)

No response

Steps to Reproduce

  1. Activate Immersive Portals version 3.0.6 for Minecraft version 1.20.1
  2. Activate Cloth Config v10 for forge 1.20.1
  3. Create a new world and enable dimension stack and place a void dimension directly above the overworld
  4. Create the world
  5. Find any structure (I've found it is more likely to happen with above ground structures)
  6. The originally named issue will be present

What You Expected

I expected the structures to generate normally, in the overworld and in their naturally generated locations

What Happened Instead

Most structures spawned at the base of the void dimension above the overworld.

Additional Details

This is the world seed of the world I used: -3524331962538916783
Both structures are within 300 blocks from spawn

Image
Image

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 does not happen on the fabric version (If it does please report to here instead).
  • I have confirmed I'm not using a hybrid server (Magma, Cauldron) or a different (non official) Forge Server release.
  • I have confirmed this issue is unique and has not been reported already.
commented

Can you please retest with the latest build?

commented

Can you please retest with the latest build?

Yes, this bug still happens on the latest build (3.0.6)

commented

Confirmed for v3.0.7 as well. Bug still exists