I’m working with the Sugar CLI tool for the first time and need some help understanding the configuration setup. I know that creator wallet addresses go in the main config file now, but I’m confused about a few other settings.
Where exactly should I put the royaltyPercentage and collectionInfo properties? Can I include them in both the main configuration and individual metadata files without causing problems?
Also, for the collection setup, does the new collection.json and collection.png approach handle everything automatically? Do I still need to add collection details to the config file or metadata files?
yep, royaltyPercentage should be in config.json, not in metadata stuff. go for the collection.json for newer setup, it auto handles everything. if you add collection info in both places, it’ll cause conflicts. just use collection.json + collection.png and leave out details in metadata, much easier.
Interesting question - I’ve been messing with Sugar CLI too and hit similar confusion.
What Sugar version are you using? Config options changed between versions, so that matters for where things go.
The royaltyPercentage usually goes in your main config.json. Have you tested this on devnet first? Best way to catch conflicts between config and metadata files is running a small test mint.
For collections - are you using an existing one or creating new? That changes how you handle collection.json. Some people add collection details to individual metadata files as backup, but I’m not sure if that’s necessary or just extra work.
Check your candy machine state after uploading to see which settings actually applied. That’ll show you what’s taking precedence.
What project are you building? Always curious what people are making with these tools!
Having set up multiple candy machines, I’ve learned that the hierarchy is straightforward. You should place royaltyPercentage in your main config.json file since that’s where Sugar looks for it, and avoid including it in individual metadata files to prevent conflicts. For collectionInfo, the newer versions of Sugar simplify this process significantly. By utilizing collection.json, everything is managed automatically. You should include your collection metadata in collection.json and the image in collection.png, steering clear of duplication in either your main config or individual files. I made the mistake of having conflicting data on my first deployment, as Sugar prioritizes collection.json, so sticking to that method keeps your setup clean and efficient.