I recently tries to get back into density function development, but faced serious issues with the generator corrupting my datapack quite frequently. It seems to happen most often when switching contexts from df generator to noise to noise settings, etc. Most often the issue seems to be that previous data that was in the editor window was written to a file it did not belong in, resulting in either data from one DF being written into another (causing strange issues) or something like a DF being written into a noise settings file, destroying its contents.
While I do not know what causes the issues, I would guess that saving to the internal file after every change may be part of it (as the issue seems to be that it saves correct data, but to the wrong file), or if not, removing automatic saves would allow the user to double check before saving over a file and breaking it.
Misode currently really is the only tool to do vanilla terrain gen development as it allows for instant feedback on settings changes, but with my datapack often breaking it has really turned me away from doing more work on my datapacks, so I'd love to see this fixed!
I recently tries to get back into density function development, but faced serious issues with the generator corrupting my datapack quite frequently. It seems to happen most often when switching contexts from df generator to noise to noise settings, etc. Most often the issue seems to be that previous data that was in the editor window was written to a file it did not belong in, resulting in either data from one DF being written into another (causing strange issues) or something like a DF being written into a noise settings file, destroying its contents.
While I do not know what causes the issues, I would guess that saving to the internal file after every change may be part of it (as the issue seems to be that it saves correct data, but to the wrong file), or if not, removing automatic saves would allow the user to double check before saving over a file and breaking it.
Misode currently really is the only tool to do vanilla terrain gen development as it allows for instant feedback on settings changes, but with my datapack often breaking it has really turned me away from doing more work on my datapacks, so I'd love to see this fixed!