Geez, I wrote that late.

It WAS the awesome.package file. Either way, I fail.<<

EDIT:
...and whaddya know? It works! Thanks so much!

I'm pretty sure that my problem is very specific.

First off, I play on a Mac.
Here is how it's configured:

Applications>The Sims 3>Show Package Contents>Contents>Resources>Transgaming>c_drive>Program Files>Electronic Arts>The Sims 3

Then, within that last Sims 3 folder is: Caches, Game, Game Data, Thumbnails, resource.cfg, and Mods (within that is Packages and framework).

I've deleted all of the cache files in My Documents. I've also tried getting the mod to work in these ways:

First, I placed my framework folder outside of the Mods folder. Putting the awesome.zip file once in the framework Mods folder and once in the root Mods>Packages folder, I ran the game (deleting my caches both times). When the awesome.zip file was placed inside the ROOT Mods>Packages folder, I got a CTD. When it was placed in the FRAMEWORK Mods folder, the awesomemod was nowhere to be found during gameplay. The enablescripterror.package file crashed the game immediately in every instance.

So, then I figured that the framework folder should go inside of the Mods folder. I did that and repeated what I had done before. When the awesome.zip file was placed in the ROOT Mods>Packages folder, I got a CTD. When it was placed in the FRAMEWORK Mods folder, the awesomemod didn't show up in gameplay.

My next thought was that maybe an existing mod was screwing around with it. I moved all of my mods to the desktop except for the awesomemod. I still had the same problem with the CTD or the mod not showing up at all. I also reinstalled my resource.cfg. Interestingly enough, when I removed the resource.cfg file from the root folder entirely, I got no CTD. However, I'm aware that my custom content wouldn't show up at all in that case.


If anyone has any suggestions, please tell me!