@Grac6 Mac-friendly fixes are the entire purpose of this section, but the fixes for bad cc are mostly the same in either OS. It does sound like you have some bad file, especially since the launcher isn't working properly. I know you removed your Mods folder, but you could still have a corrupt file somewhere else. The first suspect is your highest numbered .dbc file in DCCache, as that's where your newest cc will have landed. If removing that one file fixes your issues, you'll need to delete it and reinstall the content inside, but that's easier than rebuilding your entire TS3 game folder.
If removing the one .dbc file doesn't help, though, it's probably best to start with a clean game folder. Pull the existing one out of Documents and onto your desktop, and open the launcher to create a new one. Then you can start by copying over Mods and testing your game. If everything works, then your .package files are fine, and you can start adding Sims3Pack-based cc in batches and testing. If the launcher stops working at any point, you'll need to split and test the last batch of files you added until you find the one(s) causing the problem. There's no efficient way to identify bad content, other than testing it yourself.
It should also be noted that some of the tools used to manage cc don't work in mac OS, or work only intermittently. One of them is Delphy's Multi Installer, the usual tool of choice for converting Sims3Packs into .package files. (Another is CC Magic, which is finicky even in Windows.) What you can do though is install a pack via the launcher and then grab the .package file(s) that land in DCBackup. It's fine to rename them before dropping them in Mods\Packages; just make sure you don't change the .package extension. That way, if you get a bad cc item, you can just delete the one .package file instead of sorting through the launcher's list.
