Closed elliotdotsol closed 1 year ago
The way reveal works is that it matches the NFT number by parsing it from the name and then matches it to the number in the cache file and updates the URI to the one stored in the cache file. If your NFTs have a non-standard naming scheme Sugar's reveal
may not work and you might have to do the reveal yourself using your own script or a tool like Metaboss with a file that maps what NFT should get what new URI.
The error comes from here where it's trying to parse out the number from the collection name.
Alright thanks @samuelvanderwaal do you happen to know if Metaboss' CMv2 function works the same as CMv3? I believe it does, but would like it confirmed if you could. Thanks - after I'll close the bug report
Alright thanks @samuelvanderwaal do you happen to know if Metaboss' CMv2 function works the same as CMv3? I believe it does, but would like it confirmed if you could. Thanks - after I'll close the bug report
I'm not sure what you mean when you say Metaboss' CMv2 function. What specific command are you referring to?
For example with the snapshot
function.
For reference see:
Issue description
Hey, when trying to use the
sugar reveal
command on version 1.1.2-alpha+CMv3. I get the following error: (see code)No captures found for [Collection name], I'm unsure on what went wrong and where. Couldn't find any info anywhere on the internet as of posting this bug report.
Relevant log output
Priority this issue should have
High (immediate attention needed)