Modification Modules Question
I want my 15 rapid-fire quantum torpedo launchers Uber-Defiant now! - Get help from modders. Share your work. Discuss modifications.
posted on October 1st, 2013, 4:26 am
I'm going to try and add my mod to FO as a stand alone and had some questions. I added it already using the classic mod as a parent and everything was great with basically no issues.
Now in regards to the odf's, in stock A2 there are several sub folders for ships, stations, weapons, other etc in the odf folder. In the modding guide here it talks about having to use the odf/system hierarchy. So do I just dump all my odf's from all those sub folders into the odf/system folder in my mod so they are all just mixed in together?
Also, if the parentmod = is left blank then FO is used as the parent mod. I didn't know if this is an either/or deal. If FO is not used as a parent then I can't use anything at all from it in my mod including FO maps? What about FO weapons or explosions or shields? Also, if I do use FO as the parent then only the items I put in my actual build lists that are from FO will be used otherwise it's still all my mod exclusive items that will appear correct? I hope that makes sense.
Now in regards to the odf's, in stock A2 there are several sub folders for ships, stations, weapons, other etc in the odf folder. In the modding guide here it talks about having to use the odf/system hierarchy. So do I just dump all my odf's from all those sub folders into the odf/system folder in my mod so they are all just mixed in together?
Also, if the parentmod = is left blank then FO is used as the parent mod. I didn't know if this is an either/or deal. If FO is not used as a parent then I can't use anything at all from it in my mod including FO maps? What about FO weapons or explosions or shields? Also, if I do use FO as the parent then only the items I put in my actual build lists that are from FO will be used otherwise it's still all my mod exclusive items that will appear correct? I hope that makes sense.
posted on October 3rd, 2013, 11:00 pm
If you plan on using FO ODFs as parent ODFs, you just have to make sure your child ODFs can reference them in the correct directory. Everything else can be placed in any file system you want.
We just use the odf/system folder hierarchy because of our automatic tooling. In the next version, we'll be using the A2/A1 odf folder hierarchy again.
Parentmod refers to inheriting files. I.e. if you don't include a GUI, Fleet Ops will search for the GUI in the list parentmod. If parentmod is null (no parent mod), then no GUI will be inherited.
Parentmod only inherits things that are named the same or via the use of the #include flag.
We just use the odf/system folder hierarchy because of our automatic tooling. In the next version, we'll be using the A2/A1 odf folder hierarchy again.
Parentmod refers to inheriting files. I.e. if you don't include a GUI, Fleet Ops will search for the GUI in the list parentmod. If parentmod is null (no parent mod), then no GUI will be inherited.
Parentmod only inherits things that are named the same or via the use of the #include flag.
posted on October 6th, 2013, 3:39 am
Thanks D_N. I put my mod into FO and tried it as a stand alone, but keeps crashing. I emailed my crash log using the automated report thing. I think it was something about not finding the search directory C:\fodev\fohook something or other?
I then tried using FO as a parent, but it too crashed only it went right to desktop with no report or anything each time.
I then changed it to use the Classic Mod as the parent and it works so that's strange.
I then tried using FO as a parent, but it too crashed only it went right to desktop with no report or anything each time.
I then changed it to use the Classic Mod as the parent and it works so that's strange.
Who is online
Users browsing this forum: Google Adsense [Bot] and 3 guests