Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug] [compat] Dimension effects causes Distant Horizon to misread the dimension name and corrupt chunk caches #386

Closed
FinchPhil opened this issue Nov 3, 2024 · 0 comments
Labels
bug Something isn't working compatibility Issues with other mods neoforge Related to NeoForge

Comments

@FinchPhil
Copy link

FinchPhil commented Nov 3, 2024

Repro:

  • Install both Distant Horizon and DeeperAndDarker.
  • Create a creative world.
  • Go to the nether and explore north for a few minutes.
  • Go to the otherside, switch to spectator, go to the roof of the dimension, and look north.

Expected:
You can only see otherside chunks.

Actual:
You can see distant chunks from the nether in the distance. While this isn't much of an issue for the otherside, as it is a very claustrophobic dimension and you'll probably never see those chunks anyway, it is a major issue if you go back to the nether after exploring the otherside. Since DH shares the same cache for both dimensions, you'll see otherside chunks in the distance of the nether.

Hypothesis:
Distant Horizon uses the effectsLocation's path of a dimension to determine its name, and then uses it as a key to store its chunk caches. See: https://gitlab.com/distant-horizons-team/distant-horizons/-/blob/main/common/src/main/java/com/seibel/distanthorizons/common/wrappers/world/DimensionTypeWrapper.java#L72

I suspect that since the otherside dimension uses minecraft:the_nether as its effects, DH ends up using the same key for both dimensions, causing nether chunks to show up in the otherside, and vice versa.

Note:
I've only tested this in multiplayer (with a local fabric 1.20.1 server running in docker), but it looks like this should behave the same in single player as well.

It's unclear whether it is possible for DH to get the dimension name in a more reliable way, which is why I created this bug here instead of in DH. I assumes DH is doing the correct thing here, and is why I created this issue here instead of reporting it to DH.

@NewJumper NewJumper added bug Something isn't working neoforge Related to NeoForge compatibility Issues with other mods labels Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working compatibility Issues with other mods neoforge Related to NeoForge
Projects
None yet
Development

No branches or pull requests

2 participants