You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
on Discord, I have recently discussed an issue concerning my Shader displaying the wrong skybox on my server, on Nether and The End dimensions. What it boiled down to is that Multiverse, the plugin I use to have multiple worlds on my server, creates new dimensions for those extra worlds.
This means, that the "default" world, that is named under level-name in the server.properties file, has the dimensions minecraft:overworld, minecraft:the_nether and minecraft:the_end and the Shader works fine there, but if you add another world e.g. "world2", then the dimensions for this world are: minecraft:world2, minecraft:world2_nether and minecraft:world2_the_end and thus Optifine does not recognize the Nether or The End and tells the shader to put on the overworld skybox.
This issue added this behavior: #4287
This links to the Discord message showing the dimensions on my server: Link
I would like to request, that dimensions having the suffix _nether or _the_end are recognized as the correct world type/environment, instead of defaulting to overworld. I believe it's reasonable to assume that custom dimensions ending with these suffixes are also of those environments, everything else should still default to overworld skyboxes.
Thank you
The text was updated successfully, but these errors were encountered:
Maddin-M
changed the title
[Feature Request, Sky] Recognizing custon dimensions with _nether and _the_end suffixes
[Feature Request, Sky] Recognizing custom dimensions with _nether and _the_end suffixes
Dec 6, 2024
Hello!
on Discord, I have recently discussed an issue concerning my Shader displaying the wrong skybox on my server, on Nether and The End dimensions. What it boiled down to is that Multiverse, the plugin I use to have multiple worlds on my server, creates new dimensions for those extra worlds.
This means, that the "default" world, that is named under
level-name
in the server.properties file, has the dimensionsminecraft:overworld
,minecraft:the_nether
andminecraft:the_end
and the Shader works fine there, but if you add another world e.g. "world2", then the dimensions for this world are:minecraft:world2
,minecraft:world2_nether
andminecraft:world2_the_end
and thus Optifine does not recognize the Nether or The End and tells the shader to put on the overworld skybox.This issue added this behavior: #4287
This links to the Discord message showing the dimensions on my server: Link
I would like to request, that dimensions having the suffix
_nether
or_the_end
are recognized as the correct world type/environment, instead of defaulting to overworld. I believe it's reasonable to assume that custom dimensions ending with these suffixes are also of those environments, everything else should still default to overworld skyboxes.Thank you
The text was updated successfully, but these errors were encountered: