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]: Deformed chunk generation in existing worlds #5134

Closed
2 tasks done
LifelessAmir opened this issue Jan 29, 2024 · 4 comments
Closed
2 tasks done

[Bug]: Deformed chunk generation in existing worlds #5134

LifelessAmir opened this issue Jan 29, 2024 · 4 comments

Comments

@LifelessAmir
Copy link

What happened?

When installed ice and fire in an existing world and tried generating new chunks, it seems to be getting deformed or sorta not connect to the already existing chunks which leaves behind gigantic deformed mountains and such in the world like the picture below.
2024-01-28_23 31 24

Minecraft Version

1.19

Ice and Fire version

1.19.2-2.1.13-beta-3

Citadel version

2.1.4-1.19

Relevant log output

No response

Other Information

  • I am using other mods besides Ice and Fire
  • I have attached a log file from the session that I have experienced this issue
@SiverDX
Copy link
Contributor

SiverDX commented Jan 29, 2024

iceandfire does not touch world gen (apart from structures/features which do not cause this issue)

@DigitalWendigo
Copy link

Provide a log file and mods list, it's likely that another mod is causing the issue.

@TheBv
Copy link
Collaborator

TheBv commented Feb 4, 2024

Besides that isn't this expected behaviour from minecraft whenever the world gen changed? E.g when upgrading from different versions of minecraft.
I'll close this for now I doubt this is a iaf issue.

@TheBv TheBv closed this as not planned Won't fix, can't repro, duplicate, stale Feb 4, 2024
@SiverDX
Copy link
Contributor

SiverDX commented Feb 7, 2024

yeah big X to doubt here

affecting structures / worldgen from other mods would require some very specific code that does not exist
personally I also have not seen this issue myself in a very big modpack (with a LOT of structure mods)

Considering the lack of mass reports (which would definitely happen if this mod causes such bugs on the regular) I tend to lean on the side of you having a very specific mod having this issue which might be self-caused due to other factors

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants