So, it was a bit of a tral, I would of much rather of been playing the game instead of trying to figure out how to add mods, and try to figure what went wrong with the process. Seriously, who has the time to read all the 1000s of pages of faqs after a long day at work.

Anyway, I've added some, O-something O-/something O.. ack, don't remember what its called, supposed to make it look good. And some unofficial patch, and Vilja, who is convinced I'm wearing no clothes, despite wearing Blades armour.

I'm very tired now, don't see myself adding a lot, too much fussing.

... Cool story bra?

If you really don't have the time for even reading a mod's readme, then maybe mods are not for you. Everyone has their priorities and their preferred ways to enjoy themselves, and there's nothing wrong if playing with mods can't be among them.
If you really want to enjoy using mods, you will have to learn how to install and manage them, and as with everything in life there are no shortcuts to that: you simply have to read and learn. Is it worth it? That's something you'll have to answer yourself, preferably after trying.

Why did you install something as complex as OOO without knowing what it is or what it does?

Yep, many of us would say the exact same thing as migck. Either you need to spend time and effort to install the mods or sooner or later you will experience missing meshes and textures. On top of that you will experience the game not launching properly or CTDs. If you are okay with that then good for you.

Note: The modders put their time and effort to make mods and document it on a readme. If you can't bring yourself to read it properly and follow the instructions you shouldn't complain about mods not working or something is missing etc etc because that's why the first rule of modding for me at least is read the Readme.

Uh, you can't blame the OP. It's not as easy for Fox as it is for us. Some of us have been around Oblivion long enough that we saw every major mod come out when it came out. Others have been modding for months-years, it's pretty easy now (unless the game is Fallout New Vegas...). Seeing mods for the first time and how they work is pretty overwhelming, especially if theres a million of them out there to look at.

That being said, I have two things to say. The first is you do not have to read every word of every single readme. I've got the installation process down so well I have never read the installation page except to check what a .esp/.esm does or if I find weird files in the archive. If it is a fomod or 7-zip file/7-zip executable, I open it with 7-zip and familiarize myself with the contents. I make a new folder and paste only the .esms/.esps I want with the meshes, textures, sounds, .bsa's, etc. the mod needs. I convert that new folder into an archive and activate it with nexus mod manager. This way, no matter what the mod is, I'll have it worked out how to install and even if it replaces things without a .esp or .esm I can deactivate it with NMM and have it uninstalled without having to read the uninstallation page (although sometimes it doesn't seem to remove or deactivate the .esm - perhaps glitch). You'll have to worry about load order later when you have conflicting mods. The conflicts section of a readme is very important. As is the description. However, both things can often be skimmed through if you're careful, you don't need to read word for word. You can ignore the credits and permissions if you don't care and the readme has been convinced to a paragraph a piece (except for major overhauls).

Secondly, you absolutely cannot download anymore mods until you understand what OOO does (if thats the O-something). You NEED to know pretty much everything or you WILL get conflicts. The same rule applies for every single major overhaul out there.

Lastly, good luck. Add one mod at a time - not a hundred everytime you run the game and you'll be fine. If there's a problem, make sure you installed it in a way that makes it easy to remove so you can try again.