Describe the bug

Hello! I should start by saying that playing without these shaders are now a deal breaker for me 😄 but would like to work with Multiverse if possible.

I have am running a server locally using Paper and a few server-side mods although most of them are client-side from the Fabulously Optimized modpack and a few other hand picked.
When I started using Multiverse on this server and created a new world the shaders simply stopped working. They work just fine if I teleport back to my main world, but whenever I teleport back to another world via the Multiverse mod the shader's don't seem to affect the game at all. I have tried resetting the shader settings and toggle a few options on and off but without any luck.

In my "main" world, with the shaders working:

In an another world, with the shaders not working:

I do wonder if it's related to the minecraft world not being the regular "overworld", "nether" and "end" 🤔

Describe how your minecraft is set up

Client side mods:

Server side mods:

Describe how to reproduce the bug

• Start a new Paper server using the Multiverse plugin and generate a regular world
• Generate another world, or use the /mvcreate command from multiverse to create a new world
• Teleport to that world via /mvtp and the shaders will stop working

this is not a bug, but intentional...

i made the shader turn off in unknown dimensions, because i was getting bug reports when the shader exploded and died in some random mods dimension. i cannot possibly account for the uncountable amounts of non vanilla dimensions, so i assumed this would be better than broken visuals. turns out im getting more bug reports of the shader turning off than i got when it broke lol
so ill probably go back to how it was before, or make a basic fallback shader.

you can make the old functionality come back without much effort.

• Go into the shaderpack's file to the path: bliss-shaders-main / shaders / dimension.properties
• find the * symbol, delete it, and place a new one after the minecraft:overworld group of dimension ID's
• for example: dimension.world0 = minecraft:overworld *
  this will make any unknown dimensions use the world0 shader, which is the shader made for the overworld.

this is not a bug, but intentional...

It's not a bug, it's a feature 😄 love it!
I get it yeah I would have picked the lesser evil if I were in your place.

Seems to work like you said! If I would be allowed to suggest, perhaps adding a first-party way to add world names to the list, hidden in some settings menu, would make it easier for people like me. That being said, editing this list myself also works, so don't mind me 😛

Feel free to close this issue, since I'm happy the way it is!

without making a mod i cannot make it easier to add things to that list. shader settings do not allow inputting text or anything like that