Hey everyone! I’m new to the Sugar CLI and I’m trying to set up a Candy Machine for my NFT project. I’ve read the docs but I’m still a bit confused about a few things.
I get that the creators wallet should be in the Candy Machine config file. But what about sellerFeeBasisPoints and collection? Should these be in the config file or in each metadata file? Or both?
Also, I noticed there’s a collection.json and collection.png. Does this replace the need for a collection property in the config or metadata files?
I want to make sure I’m doing this right. Any help would be awesome! Thanks in advance!
Regarding your Candy Machine setup, it’s indeed best to include ‘sellerFeeBasisPoints’ and ‘collection’ in the config file. This approach ensures consistency across your entire NFT collection and simplifies management.
The ‘collection.json’ and ‘collection.png’ files are specifically for marketplace presentation and don’t replace the config file properties. They’re crucial for how your collection appears on platforms like Magic Eden or OpenSea.
A tip from personal experience: always run ‘sugar validate’ before deploying. It’s caught numerous issues for me, saving time and potential headaches down the line.
For a smooth process, I recommend setting up a test run with a small batch of NFTs first. This allows you to iron out any kinks in your workflow before tackling your full collection.
hey elias87! welcome to the world of sugar cli and candy machines 
i’ve been playing around with these for a while now, and i totally get how confusing it can be at first.
so, about the sellerFeeBasisPoints and collection - from my experience, it’s best to put them in the config file. that way, you don’t have to repeat it in every single metadata file. saves a ton of time, especially if you’ve got a big collection!
as for the collection.json and collection.png, those are actually for setting up your collection’s identity on marketplaces. they don’t replace the collection property in your config file. you still need that to link your nfts to the collection.
btw, have you tried running the sugar cli command to validate your config and assets? it’s super helpful for catching any mistakes before you actually deploy.
what kind of nfts are you planning to drop? i’m always curious to hear about new projects in the space!
yo elias! i’ve been there too. def put sellerFeeBasisPoints and collection in the config file. saves ya tons of time. collection.json and .png are for marketplace stuff, not replacing config properties. make sure to run sugar validate before deploying - catches mistakes quick. good luck with ur drop!