One image missing and one additional at the end?

[ultraviolet007rainbow]

Hi,

I just generated 10K again starting with 1, and ended up with 10,001 as the final image.
I went through and found out that there was a missing image at 7630.
So I edited the JSON of 10,001 to become 7630 instead as it should have been and made sure all the filenames were changed as well (JSON and Image). Will this affect the _dna.json in any way? I did identify the correct DNA line in the _dna.json that corresponds to image 10,0001 which is now image 7630. But I do not see anything in the _dna.json that would directly link it other than the traits to a specific filename (JSON or image). So is there a way to regenerate the _dna.json from the JSON files now that I have fixed the problem manually?

In addition, I found an oddity looking at the _dna.json where one of my background images I used has a numerical filename, none of the other layer files have numerical names other than this one. So in the _dna.json each one of those that has that specific background layer has 0.0 at the head of the line, which clearly is wrong. So for some reason the 0.0 was set because of the numerical layer name, is my assumption.

Is there a good way to fix this problem?

My only idea is to rename the layer to something else in every JSON file as well as the actual layer name of that specific background PNG.

And also replace all instances in the _dna.json file of that numerical layer name.

Once again will this break anything, can I regenerate the _dna.json from the altered JSON files?

Thank you for your great improvements and enhancements to the original code.

Regards.

[nftchef]

Hi! this is a very interesting and odd situation. I would be happy to look into this more if you are able to share your configuration and project on Discord. genkihagata#3074

I've never seen the generator skip a number before. It's possible that there was an error while writing the file and it was never saved, but I would need more data to reproduce it.

As for the _dna.json, it's only used for utility scripts, so it may not be that high priority to modify. It is an ordered Set (array) of all the file names used to construct each token. To modify it, you would need to find the correct index for 7630 and insert the string from the 10,001 position.

Each file name in _dna gets a prepended number map, this is how the generator navigates the subfolders. 0.0 indicates the first folder and the first subfolder for backgrounds.

[nftchef]

provenance relies on _metadata.json to read each items imageHash

_dna.json is not used in provenance, it is used in regenerate and replaceAll

[ultraviolet007rainbow]

thank you for your help with this :)

[ultraviolet007rainbow]

Okay just need to make sure because I didn't discuss this yet.
I was planning on using the util that inserts random ultra-rares into the collection.
Is this something I need the _dna.json for?
What is replaceAll? I am not seeing, I am only seeing replace.
Oh wait you mean rebuildAll, yes?
thx

[nftchef]

yes, sorry, rebuildAll
The replace util for ultra rares does not use _dna.json or modify it. any inserted rares should be done last and if you rebuild, they will be overwritten by what's stored in _dna.json. Perhaps there is room for improvement there or at least a note in the readme.

[vergara111]

indeed, it skips one number in the middle and creates extra one at the end