Metadata
Struggling to create your metadata? There are a couple of useful tools you can use to create randomly generated metadata based on your traits.
The HashLips Art Engine is a very common tool that has been around for many year. It is a very versatile program that can be used to generate your collection metadata. Simply upload the build/_metadata.json
file that it creates when you build a collection with it
https://github.com/HashLips/hashlips_art_engine
Alternatively, you can try out generatorderv2, which is a script originally created by @ItsFranken specifically for GeneratOrd. It has support for rarities and trait avoidance, so it can be used to create quite complex collections
The collection metadata file contains all the information about which traits are in each item in the collection.
It has the following format:
Here is a completed example of the Metadata JSON file.
You do not need to have the same trait types, or even the same number of traits in each item. For example, you could have an optional 'Tattoo' trait type, where some items have a tattoo and some don't. On items that don't have a tattoo, simply omit that trait, meaning they will have fewer traits than items with a tattoo.
It is important that the trait types and trait names are exactly the same as those set in the Traits tab. You must also make sure that every trait referenced in the metadata file has a corresponding trait in the Traits tab.
If either of these conditions are not met, GeneratOrd will let you know, and will not let you inscribe until you resolve the issue.
Trait Order
The order of the traits within the metadata file is very important, as this determines the order in which the traits are rendered. For example, if you have the traits Background, Head, Face and Hat, then you need to make sure they appear in that order, so they are layered in the correct order:
Unique Items
If your collection has unique items or 1/1's, you include these the same as any other item, but they just have one trait.
Last updated