-
Notifications
You must be signed in to change notification settings - Fork 25
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
Retrogen support #46
Comments
I am becoming convinced that this is a good idea, as it may also help with the deferred generation issues, which seem to break mods like Galacticraft. I could see having a save-level "version" option (like the key you suggested). If bumped, older chunks get updated. The only issue is that COG populations are not independent. Running COG twice over a chunk is not necessarily the same as running it once. So updates may not be quite the same as a fresh run. |
At least it gives a more solid approach to world-gen, allowing to recover from crashes, conflict with other mods and such. |
I'm giving another try to Custom oregen for my modpack. Have you been able to fix that issue? |
Not yet. Would you please clarify what exactly you would need for your modpack? Some sort of versioning might work. I think it would have to be associated with individual distributions, so we would know which need to be re-run. Please note that it's challenging to design distributions so that they are commutative, i.e., that they can be run again and achieve the desired effect. Adding a new distribution would be easier to configure and support. |
My main concern is to recover from crash or non-generated chunks.
|
I will try to work on this this weekend. |
Please add support for retrogen to better support existing maps and recovers from non-populated chunks.
Proposed design: add a custom NBT property to the chunk with a signature. If key is missing, no signature or different from the one set in configuration, then chunk needs a repopulation.
You could even propose a default signature that is computed as the checksum of cog configuration data so it's automatically handled (and still live the option to force the signature for fine tuning).
The text was updated successfully, but these errors were encountered: