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
Some servers have custom names for their dimensions, even though they are essentially just the vanilla dimension. This causes the mod to return the error 'Dimension {dimension} is not supported'. This is obviously intended and a necessary feature, but when the server for some reason changes the name of the vanilla dimensions it causes the mod to essentially be unable to function at all, even if it were fully able to.
Since it can happen that they are just the vanilla dimension but with a custom name, I suggest a way to manually assign the correct vanilla dimension to the custom name, so the mod can work as intended. As an example, /seedmapper:config dimension overworld will make the mod use the overworld logic for the current dimension, despite any custom naming.
The text was updated successfully, but these errors were encountered:
Well, I am glad to tell you there's already a way to do this. Instead of executing /seedmapper:locate biome badlands, just execute /source in overworld run seedmapper:locate biome badlands.
Some servers have custom names for their dimensions, even though they are essentially just the vanilla dimension. This causes the mod to return the error 'Dimension {dimension} is not supported'. This is obviously intended and a necessary feature, but when the server for some reason changes the name of the vanilla dimensions it causes the mod to essentially be unable to function at all, even if it were fully able to.
Since it can happen that they are just the vanilla dimension but with a custom name, I suggest a way to manually assign the correct vanilla dimension to the custom name, so the mod can work as intended. As an example,
/seedmapper:config dimension overworld
will make the mod use the overworld logic for the current dimension, despite any custom naming.The text was updated successfully, but these errors were encountered: