This step creates the player class on chain and stores the information needed in the configuration file.
To run, issue the following command:
The command line parameters are as follows:
The output of the help option is the following:
After this command is run, the existingClassDef
entry of the configuration file will be updated with the class definition information.
Once this command finishes successfully, you can move on to the next step
option | description |
---|---|
-e, --env
Which environment to use (devnet, testnet, mainnet-beta, localnet)
-r, --rpc-url
The RPC to use to connect to Solana. This should be a paid RPC, as this application causes heavy use to the RPC.
-l, --loglevel
The log level to use (all, trace, DEBUG, info, warn, error, fatal, off)
-k, --keypair
The keypair which is the update authority for the NFT collection
-cp, --config-path
The path to the configuration file
-h, --help
Get help with this command
This section covers the steps to use the CLI to boot-up.
This step creates the classes for the individual items that belong to the collection.
To run, issue the following command:
The command line parameters are as follows:
The output of the help option is the following:
After this command is run, classes for each of the items that you specified in the configuration are created and populated in the configuration file, ready for your NFTs to be equipped.
Once this command finishes successfully, you can move on to the next step.
This step uses the configuration file built from the previous three steps to build and equip player classes for your collection NFTs.
To run, issue the following command:
The command line parameters are as follows:
The output of the help option is the following:
PRO TIP: You can break up the running of Step 4 into parallel processes. To do this, do the following:
1) Use an external method to generate your mint list.
2) Divide the mint list into 4 separate lists.
3) Create 4 copies of your configuration file
4) Set the following keys in each of your configuration files:
5) Open up 4 separate terminals and navigate to the folder with your configuration files and wallet. Set up the boot-up step_four_create_players
command in each terminal with a different configuration file for each, like so:
6) Once each job completes, open up the configuration file for that job and update the "runDuplicateChecks" key to true, and then run the job once more to remove excess items.
After you finish "Step 4 - Create Players" and it successfully completes, you can validate using the Raindrops CLI. See the next section for an example of how to verify your Player class.
Review your Player and Item class enabling with Boots
Search for existingClassDef
in the file and copy the object into a new configuration file. We will name this bootsPlayerConfig.json for the purposes of this example.
2. Make sure you know the location of your keypair file. For our purposes, we will name this bootsUpdateAuth.json and put it in the same location as the config file from step 1.
3. You will also need the masterMint. You can find that in the "masterMint" key from the configuration file you created in step 1. For our purposes here we will be using the Mint Id BNpznqP6Rfy8LhPHEQ23qBYFiAueKiXx9jRaW6WnTo1z
4. Use the following command to show the Player class:
The result of this command is the following:
should match the number of NFTs in your collection
Should show the newBasicStats (i.e. mutationLevel) as well as the stringLayers (i.e. BACKGROUND, FUR) that you have specified in your configuration.
Shows Items that can be equipped for the NFTs in your collection.
option | description |
---|---|
option | description |
---|---|
Once you have completed all 4 steps to enable your collection to work with Boots, you can validate what your player and item classes look like by using the Raindrops CLI. First, go to the configuration file that you have been working with. You will want to copy the Player Class configuration that was generated by Boot-Up
For more detail on this output, review ""
-e, --env
Which environment to use (devnet, testnet, mainnet-beta, localnet)
-r, --rpc-url
The RPC to use to connect to Solana. This should be a paid RPC, as this application causes heavy use to the RPC.
-l, --loglevel
The log level to use (all, trace, DEBUG, info, warn, error, fatal, off)
-k, --keypair
The keypair which is the update authority for the NFT collection
-cp, --config-path
The path to the configuration file
-h, --help
Get help with this command
-e, --env
Which environment to use (devnet, testnet, mainnet-beta, localnet)
-r, --rpc-url
The RPC to use to connect to Solana. This should be a paid RPC, as this application causes heavy use to the RPC.
-l, --loglevel
The log level to use (all, trace, DEBUG, info, warn, error, fatal, off)
-k, --keypair
The keypair which is the update authority for the NFT collection
-cp, --config-path
The path to the configuration file
-h, --help
Get help with this command
This step creates the Items collection and stores the information needed in the configuration file.
To run, issue the following command:
The command line parameters are as follows:
The output of the help option is the following:
After this command is run, the existingCollectionForItems
entry of the configuration file will be updated with the item class definition information.
Once this command finishes successfully, you can move on to the next step.
-e, --env
Which environment to use (devnet, testnet, mainnet-beta, localnet)
-r, --rpc-url
The RPC to use to connect to Solana. This should be a paid RPC, as this application causes heavy use to the RPC.
-l, --loglevel
The log level to use (all, trace, DEBUG, info, warn, error, fatal, off)
-k, --keypair
The keypair which is the update authority for the NFT collection
-cp, --config-path
The path to the configuration file
-h, --help
Get help with this command