Couple Questions

[YOYOK9]

Have a couple questions.

1. The Colour for the Portal block itself. is it possible to change this from the default black? .tint only changes the screen tint when you step into the portal.

2. Would it be possible to make it so that tags worked for the portal blocks? Ex: a tag that contained the stone brick, then the portal could be made of any of the 4 stone brick types.

[wolfieboy09]

1. When I do .tint(255, 255, 255)
   
   I get the color white

And .tint(0x32A852)

Gets me this lime color

Do you have any performance mods that could be affecting it?

2. That is a good idea. With custom portal blocks, I was trying to get that working but kept getting many, many errors (screams internally), and I have reported the issue to the API: [BUG] Can't create a portal with a custom portal block AzureDoom/customportalapi-reforged#21

[YOYOK9]

Sorry for the late reply, seems to be a rendering issue with Sodium. Disabling sodium shows the proper tint.

[wolfieboy09]

No worries. Maybe see if Sodium has an option somewhere where to ignore portal block?

[YOYOK9]

Not that I can find. I had a look at sodiums config options https://github.com/CaffeineMC/sodium/wiki/Configuration-File

Seems you can disable different mixins used, but I am not sure what portal blocks would fall under.
https://github.com/CaffeineMC/sodium/blob/dev/common/src/main/java/net/caffeinemc/mods/sodium/client/data/config/MixinConfig.java#L1C1-L91C1

[wolfieboy09]

go thru every mixin config and find out

This is the mixin that gives the portal it's color
https://github.com/AzureDoom/customportalapi-reforged/blob/3bbe98983cf958e9e8e36f9c43ce22e1bde1dffa/src/main/java/net/kyrptonaught/customportalapi/mixin/client/WorldRendererMixin.java#L18-L34

And looking at Sodium config, I'm guessing features.render.world would be the closest to fixing it

[YOYOK9]

Tried the mixin you mentioned, still had the issue. Ended up just biting the bullet and disabling all but the following:

mixin.features.textures=true
mixin.features.textures.animations=true
mixin.features.textures.mipmaps=true

As a new world would crash in general without those enable. Still had the same issue.

Extra info:

For simplicity reasons I trimmed down my other packs custom world datapack to a simple vanilla world using Mojang's Dark Green colour code (Just incase it didn't like my custom colour)

The following log contains mods I used while troubleshooting:
Neoforge - 21.1.127
Custom Portal API Reforged - 1.21.1-1.0.11
Kubejs - 2101.7.1-build.181
PortalJS - 1.0.3
Rhino - 2101.2.7-build.74
Sodium - 0.6.9

I enabled sodium's normally false debug mixins as well, just to see if it could help show more in the logs?

mixin.debug.checks=true
mixin.debug.checks.threading=true

Latest.log

Debug.log

My Sodium-mixins.properties file If needed

[wolfieboy09]

Wait a moment, I thought that mixin from CPAPI was the correct mixin (that mixin is for sounds).
The correct mixin is this class: https://github.com/AzureDoom/customportalapi-reforged/blob/3bbe98983cf958e9e8e36f9c43ce22e1bde1dffa/src/main/java/net/kyrptonaught/customportalapi/mixin/client/InGameHudMixin.java

I'm sorry, I thought that was the right one but this one is the right one 😭

[YOYOK9]

Would this be something I would need to open with the CPAPI dev? or sodium? My mixin (or mod dev) skills aren't the greatest, so not overly sure where to go from here?

[wolfieboy09]

I asked in the Sodium server (that is "Caffeine MC"): (thread: https://discord.com/channels/602796788608401408/1346460473872355409)

And nothing since then.

[YOYOK9]

Thought I would give a bit of an update. Someone made a Neoculus port, meaning I could switch from Iris and Sodium, to Neoculus and Embeddium.

I know Embeddium is a port of Sodium, but I figured I would let you know the issue happens with Embeddium as well. Not sure if you might get a better answer from the Embeddium dev Vs Sodium?