Closed frikinjay closed 3 years ago
Well this is an odd one. Did you register another portal to the aether? Can you post the relevant code?
I think this is caused by custom portal block used by the aether. It has a hard link to the glowstone block as the frame. You'd have to create a new portal block or just use the default. I guess I never thought of having portal of different types linking to the same dim
Yeah i basically used Aether's portal block directly as the custom portal block. I think i might have a hint as well, it doesnt look like its hardcoded in the class where it extends CustomPortalBlock
CustomPortalBuilder.beginPortal()
.customPortalBlock((AetherPortalBlock) BLUE_PORTAL)
.frameBlock(Blocks.SHROOMLIGHT)
.lightWithWater()
.destDimID(new Identifier("the_aether:the_aether"))
.tintColor(50,133,168)
.flatPortal()
.registerPortal();
This is it hardcoded to always return a gowstone block as it's frame. his helps with performance. You can not supply a customPortalBlock to the builder and it will just use the default one. Which should work fine
I originally had the default one but I was hoping to use Aether's for the proximity sound triggers, particles, other effects etc. I might have to just recreate a class without the glowstone requirement and use that with the AetherBlocks BLUE_PORTAL
Seems to work fine without the override
Do you want me to close the issue? This is intended right?
Yes, it technically is intended behavior. Just very odd when used like this
Ah i see no worries. Thanks for the help!
Not sure if its been implemented properly yet for flat portals but when going into the portal for the first time it generates a weird portal on the other end and if you go through that portal the game crashes with this. (Using the most recent commit of both The Aether and CustomPortalAPI)
https://user-images.githubusercontent.com/88995340/140008934-49afb839-7b29-480b-b5f1-ad1f14a0605e.mp4