Ah right, no problem
I'm just curious that's all
My friend is the worst when it comes to modded minecraft. He can't get the FTB launcher to work, he can't be bothered to learn new mods, he doesn't like revamp mods (Thaumcraft 4 instead of TC3/TC2, etc.) and it's just one of those frustrating things. If he took a minute or two to think about stuff, and maybe google it, or thought about what may have caused the issue (when he attempts a mod and it doesn't work) for a few minutes, and was logical about it, he would have a lot more fun
Same goes for modded minecraft.
If something goes wrong, take a step back.
If you took a big step (adding 4, for example, mods at once), retake those steps slowly (re-add one at a time)
If you get a crash report, it's line 7 (when you put it in pastebin) that tells you what is the issue (always copy and paste the crash report out of the generated notepad file into pastebin, it's so much easier to read)
If you are using a texture pack, and a mods' texture is messed up (in game) then swap to default to test.
Just a few things that sound really basic, but people forget to do it. And since modding minecraft is so much easier in 1.7 onwards (no more item ID conflicts) these few tips are usually enough to get you by. Obviously if you get a horrible report on line 7 which you don't understand e.g.:
cpw.mods.fml.common.LoaderException: java.lang.ExceptionInInitializerError
Then obviously, there is nothing wrong with running around screaming