It’s been awhile since I’ve modded FL (getting back into it myself, actually, :P) but I can agree with Xarian_Prime. To become better, you will first be broken. I remember many times booting FL only to have it either CTD immediately upon opening a new menu, or mid-game when I happened to actually do something. Makes you fear the CTD and cross-fingers.
But the more you fail, the more you learn. Yes, you learn with success too, but not in the same way. Learning when failing makes you more cautious and less code-happy until you gain what you consider enough confidence to dive into deeper ends, and from there, with confidence strapped to your belt you can achieve many things, :).
Rather than purely listing my opinion on knowledge you need I will just give tips (albeit generic, still handy and from which I’ve learned):
Tip #1: Save a ton of tutorials and if some seem like they will fit in with your current mod, try to implement it. The more you implement things on the coding-side the more confidence you will get poking within FL’s depths. There’s quite a few here at The-Starport and there are more within their Freelancer Archived site (http://www.the-starport.net/archive/). From engine trails to making factions, try to archive anything and everything. Who knows how much longer the information will be around.
Tip #2: Rather than dive into a serious mod that you really want to make, make a mod you can use as a testbed. Try out tons of tutorials and see if you can get them working. As each works, implement into the mod you like. This helps avoid disillusionment and keeps your eventual goal alive, rather than having your ideal mod crashing constantly because of new, untested implementations.
Tip #3: Patience is a virtue. If you aren’t patient, take breaks when your code isn’t working (make a comment/file somewhere saying where you’re at so you don’t forget). Listen to music while modding to try and take some edge off, maybe. That way you are relaxed enough to tackle it again later, rather than getting so worked up that you throw in the towel.
Tip #4: Don’t view failure as an issue. View it as a challenge, :). Brainstorm ways to try and correct any issue, try them and cross them off as you go.
My post might not have been the most informative, but it’s my limited insight into enjoying modding and hopefully it’ll guide you to also enjoy it.