How to include manually generated NFTs in the collection?

[purpleglow]

Say I have generated 3,333 NFTs with random attributes, and I'd like to add 10 that are manually generated. How would I go about doing that, please?

[ovrlnd]

Also wondering about this! Say I've generate 1000 NFTs with random attributes using this program, and I want to generate 1000 more with the different layers but upload 2000 all at once, how would I do that?

[alyhandro]

-If you're only adding 10, could you just take you top 10 rarest and the edit the .JSON manually and replace your corresponding PNG?

-Or could you add your 10 manual NFT using 10 separate 'growEditionSizeTo: 1,' and then do something like this:

{ name: "body manual-1", options: { displayName: "Body" } },

.. so that it selects your manual layers but still gives it the trait of 'body' in the metadata.

I'm yet to try this and don't have much coding experience so it could all be wrong 🐙

[Sp33dyFoX]

I just tried this to test the theory. It worked for me. There are a few steps hopefully it makes sense. I used my file explorer to perform the following tasks:

1.) Make a separate folder with copies of the layers you used to make your build.

2.) Copy the "build" folder from your current build to a clearly labeled new folder for safekeeping.

3.) Go back to the Hashlips "layers" folder and delete the specific layers you don't want to see in your custom NFT or add new ones that you do. You could simply save a hand-made png into your "Background" folder and save a few blank png files in the other layers folders with names describing your artwork as hand-drawn eyes, hand-drawn hat, custom hoodie, etc. You can set your rarity as 1 for each layer. Then you still have properties that show up for your artwork.

4.) Run Hashlips to generate the specific combination you desire complete with an accompanying json file. The json file contains the dna specific to the image you generated.

5.) Move your custom NFT's "build" folder into a safe new folder.

6.) Copy your original "build" folder back into the Hashlips folder.

7.) Rename your custom NFT and accompanying json file as one of the numbers from the randomly generated set in your original "images" and "json" folders. You're going to replace both.

8.) Copy and paste your custom NFT into your "images" folder (it will ask you if you want to replace the existing file with the same name, click Yes. Do the same with your custom NFT's json file in the "json" folder.

9.) Now, in theory, you should have the same amount of NFTs and json files in your original "images" and "json" folders including your custom NFT. All of their attributes should show up in your Hashlips Art Engine. You can check this by going to the folders list on the left side of Visual Studio Code with your Hashlips Art Engine and checking to ensure that your custom NFT json file lists the correct attributes displayed in your custom NFT's artwork. The json file is important, without it all you have is a picture.

Hope this helps

[swolswolomon]

If you want to force the background to always be black (as an example), create a new folder called Background2 and place only one trait inside of it. Then inside the layer configurations, add a configuration with a growEditionSizeTo: 1 and set the displayName to 'Background'. If you don't set the display name, then the json data will have a "Background2" trait. Do this for all your manual NFTs, then follow these with a growEditionSizeTo your total collection size. Now your manually created NFTs will always be in the beginning followed by the randomly created versions.