Creator Defaults are used to add default values that limit the options a user can select when personalizing their background. For example, you may only want your background to have a pink or blue border because it matches the color scheme. You can do this using creator defaults. To edit these settings, click the “Edit Creator Defaults” button.
First, you’ll notice two buttons in the top left corner, Designer and JSON . Designer is your visual editor and will show you, in real time, how your defaults will look. If you prefer to add these in code, click the JSON button. To choose between different categories of the designer, click the button below the Designer and JSON buttons. This will display a dropdown list with different options. These options include PFP, Text, Background and QR. We’ll go through each option to get you familiar with them.
The first option is PFP. This lets you set defaults for the Profile Picture area of the Handle.
- "Upload Test Image" lets you upload an image of your choice to see how it will look. This is especially useful when using the zoom option.
- Zoom lets you control the zoom and pan of the PFP image.
- Border lets you set one or more colors to limit the options for the user. To enable click the toggle, then click the Plus button. Use the color picker options to pick a color that looks great with your background.
Once you save a color, you can easily delete it by hovering over the color and clicking the trash can icon. The colors you add will become options that the user can choose from. Remember, the user has the option to turn off your settings unless you have the “Force Creator Settings” option checked. We’ll talk more about this in the "Editing Creator Defaults Other” section. Regarding the color options, most of the color select interfaces will behave this way. Some however, are limited to only one color.
The next option is Text. This lets you set defaults for the Text area of the Handle.
- The test_handle field lets you change the Handle name. Use this to check your font for ambiguous characters. These are characters that look like other characters. For example, a capital O and a 0. If these look too similar, your collection may be removed until this is fixed to prevent User issues.
- Font lets you add a custom font. This needs to be a link to a tiff or woff file. https://fonts.cdnfonts.com/s/57197/times.woff
- Color lets you change the color of the Handle name. This is limited to one color.
- Shadow options lets you set the horizontal, vertical and blur of the text shadow.
- Ribbon Colors lets you set the text ribbon which appears behind the Handle name. This option has 2 features. You can either display multiple colors to limit the users options or you can elect to use the gradient feature. The gradient option will use your selected colors and gives you two additional options, a number used as a degree for the linear option and radial.
The Background option lets you limit the colors for the Handle Image border.
The QR option lets you dial in the look of the QR code.
- Background lets you choose one color for the QR code background.
- Dot Color lets you choose the color and the type. Type includes: square, rounded or dot. We’ll use a rounded theme.
- Inner eye and outer eye are similar to dot color.
The “Other” option gives us additional features for our defaults.
- Remove Dollar Symbol is used if you have a custom dollar symbol in the top right corner of your background.
- Force Creator Settings takes away the users ability to change personalization settings to anything other than what you have specified. This ensures users will follow your guidelines.
-
The Asset Requirements option requires the user to have specific collections and assets before purchasing your background. For example:
- “Require Collection Policy IDs” enables the ability to require a wallet to contain an asset from the policy and optionally starts with an <asset_prefix>. This is how a project can associate a particular background with particular NFTs. Multiple values are treated as an “Or” match.
- “Required Asset Attributes” enables the ability to require a wallet to contain an asset that has a CIP-0025 or CIP-0068 NFT attribute that matches the key:value. This would usually be combined with the above require_asset_collections. We will first consider metadata/datum attributes located in an ‘attributes’ map. If not located there, we will look for any key:value match on the root of the metadata/datum. This is similar to the way CNFT marketplaces filter attributes. Multiple values are treated as an And/All match. Note: For CIP-0025 PFP NFTs, we can only validate in the front-end and back-end off-chain code. We cannot validate CIP-0025 data in the smart contract.
- The Require Asset Displayed option is intended to be combined with the above two settings. If enabled, the user also has to select the asset to be displayed in their Handle (not just in their wallet).
For example, let’s say a user must own a Clay PFP with a red shirt in order to purchase this background. First, I’ll add the policy Id, 40fa2aa67258b4ce7b5782f74831d46a84c59a0ff0c28262fab21728, then the key value pair, clothes: Tshirt Red.
Once you have finished adding your Creator Defaults, click the “Save and Close” button.
Finally, click the “Mint Asset” button.