I think I understand FOMODs... or at least how to make things compatible with Fallout Mod Manager (FOMM). From my understanding, the basic idea is that you structure your ZIP (or 7z or Rar) file as:

Mod.esp (your mod's ESP file)ReadMe - Mod.txt (your ReadMe document)fomod/info.xml (title, author, category, version information)

At least, that's how I structured my release ZIPs (uploaded as .zip instead of .fomod due to Fallout3Nexus rules).

Now I have a few questions:

1) If I want to include additional ReadMe type files in the ZIP, but don't want them to get installed to the Fallout 3 program folder, do I just put them in a sub-folder inside the ZIP and FOMM will ignore them?

2) Are there any issues with naming the file .ZIP instead of .FOMOD since FO3Nexus won't let me upload as ".fomod"?

3) If I stay away from scripting, do I need to care at all about the FOMM version? I think the answer here is no.

4) Any problems with assembling the ZIP by hand, including editing the info.xml file with a text editor?

Don't rename the file. That will screw all sorts of things up. Just pack the .fomod in a rar archive and be done with it.

As for the readmes, as long as they're not part of the fomod FOMM will ignore them entirely. So you can have readme.txt and .fomod in the same RAR archive and FOMM will only worry about the contents of .fomod

Unless you follow TestECulls advise, you are going to have to make a custom install script to get FOMM to not install the readmes.


No, a FOMOD file is just a ZIP with the file extension renamed.


As far as I know, you are right. No scripting means that FOMM version should be pretty unimportant.


No. In fact, this is the way many of us do it