Skip to content

Immersive Portals Improvements - #640

Open
Jeryn99 wants to merge 12 commits into
dev/1.20.1from
ip-improvements
Open

Jeryn99 wants to merge 12 commits into
dev/1.20.1from
ip-improvements

Conversation

@Jeryn99

@Jeryn99 Jeryn99 commented Sep 7, 2026

Copy link
Copy Markdown
Collaborator

Started on this a while ago and rewrite the Gravity Shaft UI and the Shell View UI

Ended up fixing IP placements, bon appetite

Note: As @Acuadragon100 has committed a lot I have had to merge his changes in and had merge conflicts, would benefit from a closer view to ensure his changes got in

if(ModCompatChecker.immersivePortals() && ImmersivePortals.isTeleportingPortalPresent(shellBlockEntity.getTardisId())){
return Shapes.empty();
}

@Acuadragon100 Acuadragon100 Sep 7, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With this we can probably remove my IP_VS_COLLISION config check just below this (in hindsight we should probably move that config to SERVER anyway (we can't remove it completely since the interior door is still using it right now, but maybe we can just remove the collision box for the interior door as well and get rid of the config?), I didn't realise Forge Config API had automatic config sync for SERVER configs when I wrote this code). I can fix that later though.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, I found a bug here. It's the same bug which I have a fix for in #625, but it happens every time a TARDIS is created.

Basically, when creating the TARDIS, the dimension parameter will be null, and isTeleportingPortalPresent expects a not null value.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we merge both this and #625 it should just solve itself though.

/* if (ModCompatChecker.create()) {
CreateIntergrationsInit.init();
}
}*/

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Umm... Any particular reason why you disabled the Create compatibility?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will correct this, I was making a build for someone who was using a older create version, pay it no mind

@Acuadragon100

Copy link
Copy Markdown
Contributor

Welp, I think this is good enough to merge, probably. I only found one bug which should fix itself once we merge one of my other PRs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants