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]: Weird Generation with Dragon Roost - 1.18.2 #5057

Closed
2 tasks done
wabeb325 opened this issue Dec 31, 2023 · 4 comments
Closed
2 tasks done

[Bug]: Weird Generation with Dragon Roost - 1.18.2 #5057

wabeb325 opened this issue Dec 31, 2023 · 4 comments

Comments

@wabeb325
Copy link

wabeb325 commented Dec 31, 2023

What happened?

When you explore new chunks with the last beta of 1.18.2, all the dragon roost gets spawned like this:

image
image

Btw, I'm using Terralith and I don't know if this happes in other scenarios.

Minecraft Version

1.18

Ice and Fire version

Beta Release 1.18.2-2.1.13-beta-2

Citadel version

citadel-1.11.3-1.18.2

Relevant log output

No crash was experienced, so no log, is just world generation.

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
@TheBv
Copy link
Collaborator

TheBv commented Jan 2, 2024

I can't seem to replicate this.
Do you have any other worldgen/optimisation mods installed?
Or maybe running a non vanilla server like magma?

@wabeb325
Copy link
Author

wabeb325 commented Jan 2, 2024

No other world generation mods except Terralith, Abnormal mods and BOP, and I was running this in my computer (client side) but I already tested this in a forge server and it happens as well, I'm using embeddium, ferritecore, lazyDFU, modernfix, memory leak fix and Ksyxis as performance mods. I'm going to try if it works without them.

@TheBv
Copy link
Collaborator

TheBv commented Jan 2, 2024

Yeah otherwise if you have a seed and coordinates that'd be great :)

@wabeb325
Copy link
Author

wabeb325 commented Jan 5, 2024

I already tested the new version and somehow this error was hopefully fixed.

@wabeb325 wabeb325 closed this as completed Jan 5, 2024
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

2 participants