Step 5 - Verification
Review your Player and Item class enabling with Boots
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. An example of a finished configuration file is in the Examples, here. You will want to copy the Player Class configuration that was generated by Boot-Up
- 1.Search for
existingClassDefin the file and copy the object into a new configuration file. We will name this bootsPlayerConfig.json for the purposes of this example.
1
{
2
"data": {
3
"settings": {
4
"defaultCategory": {
5
"category": "panda",
6
"inherited": { "notInherited": true }
7
},
8
"childrenMustBeEditions": {
9
"boolean": false,
10
"inherited": { "notInherited": true }
11
},
12
"builderMustBeHolder": {
13
"boolean": false,
14
"inherited": { "notInherited": true }
15
},
16
"updatePermissiveness": [
17
{
18
"permissivenessType": { "tokenHolder": true },
19
"inherited": { "notInherited": true }
20
}
21
],
22
"instanceUpdatePermissiveness": [
23
{
24
"permissivenessType": { "parentTokenHolder": true },
25
"inherited": { "notInherited": true }
26
}
27
],
28
"buildPermissiveness": [
29
{
30
"permissivenessType": { "tokenHolder": true },
31
"inherited": { "notInherited": true }
32
}
33
],
34
"equipItemPermissiveness": [
35
{
36
"permissivenessType": { "parentTokenHolder": true },
37
"inherited": { "notInherited": true }
38
}
39
],
40
"addItemPermissiveness": [
41
{
42
"permissivenessType": { "parentTokenHolder": true },
43
"inherited": { "notInherited": true }
44
}
45
],
46
"useItemPermissiveness": [
47
{
48
"permissivenessType": { "parentTokenHolder": true },
49
"inherited": { "notInherited": true }
50
}
51
],
52
"unequipItemPermissiveness": null,
53
"removeItemPermissiveness": null,
54
"stakingWarmUpDuration": null,
55
"stakingCooldownDuration": null,
56
"stakingPermissiveness": null,
57
"unstakingPermissiveness": null,
58
"childUpdatePropagationPermissiveness": []
59
},
60
"config": {
61
"startingStatsUri": null,
62
"basicStats": [
63
{
64
"index": 0,
65
"name": "mutationLevel",
66
"inherited": { "notInherited": true },
67
"statType": {
68
"enum": {
69
"starting": 0,
70
"values": [
71
{ "name": "NA", "value": 0 },
72
{ "name": "Lvl1", "value": 1 },
73
{ "name": "Lvl2", "value": 2 },
74
{ "name": "Lvl3", "value": 3 },
75
{ "name": "Lvl4", "value": 4 }
76
]
77
}
78
}
79
},
80
{
81
"index": 1,
82
"name": "BACKGROUND",
83
"inherited": { "notInherited": true },
84
"statType": { "string": { "starting": "unset" } }
85
},
86
{
87
"index": 2,
88
"name": "FUR",
89
"inherited": { "notInherited": true },
90
"statType": { "string": { "starting": "unset" } }
91
}
92
],
93
"bodyParts": [
94
{
95
"index": 0,
96
"bodyPart": "GLASSES",
97
"totalItemSpots": 1,
98
"inherited": { "notInherited": true }
99
},
100
{
101
"index": 1,
102
"bodyPart": "DUMPSTER",
103
"totalItemSpots": 1,
104
"inherited": { "notInherited": true }
105
},
106
{
107
"index": 2,
108
"bodyPart": "BODY",
109
"totalItemSpots": 1,
110
"inherited": { "notInherited": true }
111
},
112
{
113
"index": 3,
114
"bodyPart": "HEAD",
115
"totalItemSpots": 1,
116
"inherited": { "notInherited": true }
117
},
118
{
119
"index": 4,
120
"bodyPart": "MOUTH",
121
"totalItemSpots": 1,
122
"inherited": { "notInherited": true }
123
}
124
],
125
"equipValidation": null,
126
"addToPackValidation": null
127
}
128
},
129
"metadataUpdateAuthority": null,
130
"storeMint": true,
131
"storeMetadataFields": true,
132
"mint": "GmSRDXiXgvNo7UEx3rNvPCqD6aSreJaXT51tfq6ATXTK",
133
"index": 0,
134
"updatePermissivenessToUse": { "parentTokenHolder": true },
135
"namespaceRequirement": 1,
136
"totalSpaceBytes": 739
137
}
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
BNpznqP6Rfy8LhPHEQ23qBYFiAueKiXx9jRaW6WnTo1z4. Use the following command to show the Player class:
player-cli show_player_class --env devnet \
--rpc-url https://api.devnet.solana.com \
--log-level debug \
--keypair './bootsUpdateAuth.json' \
--config-path './bootsPlayerConfig.json' \
--mint BNpznqP6Rfy8LhPHEQ23qBYFiAueKiXx9jRaW6WnTo1z \
--index 0
The result of this command is the following:
wallet public key: 2crTqcmVJVMW6b5z6NEs9HdsKmVc4zDDE2FucNg98kSN
USING CUSTOM RPC URL: https://api.devnet.solana.com
Player Class 9QQgCvCzuveTtdUb6is3BTsexsWYrGDoxdb51tzz62tH
Namespaces: [ undefined ]
Parent: None
Mint: BNpznqP6Rfy8LhPHEQ23qBYFiAueKiXx9jRaW6WnTo1z
Metadata: CgAzk9iFnciye3yoh1bufFbeQWgadtFjx9C4E73mEYP4
Edition: Dj4gasLLVoKLd8D8rQoHwFHbGwkMPbsHD8bR455aYwqR
Existing Children: 1
Player Class Data:
--> Player Class Settings:
----> Default Category (notInherited): panda
----> Children must be editions (notInherited): false
----> Builder must be holder (notInherited): false
----> Update Permissiveness:
------> (notInherited) tokenHolder
----> Instance Update Permissiveness:
------> (notInherited) parentTokenHolder
----> Build Permissiveness:
------> (notInherited) tokenHolder
----> Equip Item Permissiveness:
------> (notInherited) parentTokenHolder
----> Add Item Permissiveness:
------> (notInherited) parentTokenHolder
----> Use Item Permissiveness:
------> (notInherited) parentTokenHolder
----> Unequip Item Permissiveness:
----> Remove Item Permissiveness:
----> Staking warm up duration: Not Set
----> Staking cooldown duration: Not Set
----> Staking Permissiveness:
----> Unstaking Permissiveness:
----> Child Update Propagation Permissiveness:
--> Player Class Config:
----> Starting Stats Uri: Not Set
----> Basic Stat Templates:
------> Index: 0
------> Name: mutationLevel
------> Stat Type: Enum (Start: NA)
------> Values: NA => 0,Lvl1 => 1,Lvl2 => 2,Lvl3 => 3,Lvl4 => 4
------> Inherited: notInherited
-------
------> Index: 1
------> Name: BACKGROUND
------> Stat Type: String (Start: unset)
------> Inherited: notInherited
-------
------> Index: 2
------> Name: FUR
------> Stat Type: String (Start: unset)
------> Inherited: notInherited
-------
----> Body Parts:
------> Index: 0
------> Inherited: notInherited
------> Body Part: GLASSES
------> Total item spots: 1
------
------> Index: 1
------> Inherited: notInherited
------> Body Part: DUMPSTER
------> Total item spots: 1
------
------> Index: 2
------> Inherited: notInherited
------> Body Part: BODY
------> Total item spots: 1
------
------> Index: 3
------> Inherited: notInherited
------> Body Part: HEAD
------> Total item spots: 1
------
------> Index: 4
------> Inherited: notInherited
------> Body Part: MOUTH
------> Total item spots: 1
------
-------
------> Equipment Validation Callback: Not Set
------> Add to Pack Callback: Not Set
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.
Last modified 6mo ago