#Locking Terralith generation to specific world(s)
13 messages · Page 1 of 1 (latest)
Thanks for creating a thread! Be patient, and we will answer your question when we are able to. In the meantime...
• Check the FAQ by doing /faq to see if your question is already answered.
• Did you describe your issue thoroughly?
• Are relevant logs attached?
• Is your thread tagged appropriately?
• Ensure you've answered the questions outlined in our Post Guidelines.
When your question is answered, please close it with /close, or click the button. Thank you!
Not feasible
The overrides in the minecraft namespace are vast and you'd need to add a bunch of extra files as well
It doesnt seem that unrealistic after looking into it. It wouldn't be very version-friendly, but moving terralith's worldgen, etc. to a new dimension seems to be doable. As for adding extra files, what extra files would I need to add? I was under the impression that I just need to move around some files and rename symbols
It doesnt seem that unrealistic after looking into it
The problem is you need to move all theminecraftoverrides to another namespace and then only redirect those file references
and a lot of files (particularly the noise/density function ones) don't have their default files shipped
there's no list of those files you'd need to put in, you have to figure it out on your own
This is a working example I put together. I had to move all the minecraft overrides into a separate dimension and piece back together every reference. There was a lot more involved in it but it's just a POC, I guess. My main goal was to not pollute vanilla worlds/dimensions in any way so I did have to sacrifice a few features of Terralith.
This is running on a Folia based server too so I also had to remove data/terralith/functions