The two folders you are referring to would be the base game installation directory, i.e. C:\Program Files\Electronic Arts\The Sims 3 (or something similar dependent on your operating system and whether or not you chose a default installation) and the installation directory for the expansion pack if you have it, i.e. C:\Electronic Arts\The Sims 3\World Adventures.  The resource.cfg file would be moved with the actual mod file(s), but would be placed directly in the installation directory as opposed to within Mods>Packages.

I don't get what is so hard to understand.  Read the thread "How To Install The Framework & AwesomeMod". http://www.moreawesomethanyou.com/smf/index.php/topic,17454.0.html

Yup. Looks like WA will remain uninstalled untill I can figure something out.

Thanks for your help though

EDIT - Panic over... it now fucking works!! I uninstalled WA, ran the base game, fine, re-installed WA, put the framework files into both folders, except the cfg file,  ran it again and wallah... we have an updated, working game with the expansion pack installed...

Now after all that hassle, I dont even want to play the pissing game. Im sick of the sight of it... ARGH

Heh heh, at least you were able to actually play WA Lorea.

I can't even install mine. 

Here's the official word regarding Error 16:

We have been made aware of an issue you may encounter while trying to save your game after installing The Sims 3 World Adventures or updating your game. The Sims 3 World Adventures and the Game Update have changed the way your save files are created, which can lead to an error during your gameplay when you save your game. If you encounter an error that says "Error Code 16," please use "Save As" to save your game instead. This will allow you to create a new save file and circumvent this error.

If you are beginning an entirely new game or starting in a new neighborhood, you will NOT encounter this issue.

We are working to address this and will update you as soon as possible.

Thanks,
-Big Guy-

Something seems very wrong if your neighborhood is 89 MBs.

Prior to this happening, I noticed that the path finding AI of some sims are disabled. When I direct them to a door, they go straight to that direction and stop in front of a wall that is between the sim and the door. And visiting neighbors, the ring doorbell becomes inaccessible and only functional if you do it outside of the neighbor's lot. Succeeding in ringing the doorbell, the neighbor inside the house just keep doing what it has been doing ignoring the bell. I had similar experience two months before and it also ended up in an error 13 and then error 12.

Have you tried removing all the hacks / mods and Custom Contents as well as store items and just play the game vanilla? A patched game would be okay. Sometimes playing it without hacks will reveal what problem is causing the error 12s. Though in my case removing the hacks the game started going weird seemed like a nightmare. But that experience showed me what's really causing my game to bug.

Also, could you recall any mods that you removed before having this error problem? I tried Kolipoki's Plant roasts and links mod when I removed them days after, my sims started getting bugs. Do you have any similar incidents?

If you do have any hacks removed, maybe it is better to reinstall the game and only apply the patch and re-load your old save and play normally.

Another suggestion, if you have the time try going into every lot in the game and see if there are immovable graves inside or any weird stuff that you'll consider a bug. Try deleting those you deem irrelevant and problematic. It will not only reduce possible / potential error 12s but also help in error 13s. I mentioned immovable graves because some sims die inside the lot and the game failed to transfer it to the mausoleum, it will register to the game as default graves like Eric Darling's (crumplebottom) grave or the ones at the cemetery. For my game, the tombs at the Jones and Goth houses are movable but Eric Darling's isn't.

Have you tried using s3rc to ensmallen and debloatify your saves? It's possible that there is sufficient retained cruft to overload the save process.

Are you selecting the same sim all those time you use the Simselector before the error 12 appear?

Error 12s are game corruptions that unfortunately writes into the cache.

Deleting the world cache files will result to a slow game start up as a new cache is being written. The game will lag and freeze as the cache is being re-written. But deleting it will only temporarily resolve Error 13s not Error 12.

It's not very clear what sort of game corruption results to Error 12. My guesses are bad sim descriptions, bugged interactions, mod incompatibilities and missing sims, bugged aging states and there are some more unidentified ones. One solution is just to continue playing and pray hard that the corruption gets overwritten. Awesomemod has an exprimental debug command that helped a player resolve the error, but personally, I have not yet tried it so I cannot recommend it for now. Quitting the game and reloading a previous save game is the most safest way right now, just save frequently every 15 minutes.

For those experiencing Error 13s it is caused by the cache being over stuffed with textures and game objects loaded. The more sims, textures and objects in your game world the more faster the cache gets overloaded and resulting to Error 13s. Turning off reflections, reducing graphics quality and removing wants on the current household or deleting unneeded lots/objects can help resolve Error 13s.

For Sunset Valley: It is located in the main folder under caches filename: Sunset Valley.objectCache (Do not delete unless you really know what to do, this cache does not regenerate once deleted. You'll have to re-install the whole game if you do)

For Riverview: It is in the save folder, World Cache, Riverview_sim.package & Riverview_object.package (Deleting this will result to game slow downs and lagging while it is being re-written back, Do not freak out when textures are all dark gray, it will eventually return to normal depending on your computer's specs.)

Error 13 is a memory problem. The game limits the cache to 1GB. So far whatever settings you do with the game it will still be at maximum of 1GB. However, if you are using Riverview, there are some reports that it can go a little bit over 1GB but not much maybe a few Mb at the most.

If your neighborhood is overpopulated with sims, very high graphics settings or lots of overstuffed, over decorated houses error 13 will not be far behind.

Every actions of sims are written in the world cache. Every texture, every object as well is written there.

Guessing by the description of Error 13 = Post Save Callback failure, it may probably mean that after saving, the game rechecks stability of the save and fails due to insufficient cache space to load the save or it's a bad save.

If you do multiple save games, you'll notice that if you have error 12 the *.bad save file will be around 40-60% of the good save file size, but if you have error 13 you'll have around 90-95% of the size of a good save file.

We are actively looking into that, yes. In fact, I wrote something to ostensibly pause the game, do the save, and then unpause, but apparently it doesn't always stick in the autosave.

Extract the text files from Awesomemod, edit them to your language, import in a new package. Place this package in a folder with higher priority than AM.

How can I translate new trait's names and definitions (not to be different from others)?
Maybe with S3Pe?

I also thought it was already happening. 

I know many of my inactive sims have gotten fitter/buffer looking over time.  Not all, but a good number have.  I think it depends on how often the game sends them to workout.