I should be recommending the standard though so will also have a look at presentation of this. You have assumed that people already know how the UOP is packaged and what it contains.īereket Fekadu Posts: 3421 Joined: Thu 10:41 pmĭid not know that :blush2: - But, with newcomers to BAIN, having a ReadMe in the root of the folder will be the first thing they see if they have extracted it instead of just throwing it into Bash Installers - And my train of thought is ( hopefully they will read that, ahem ) they will realise they did not need to extract it in the first instance. The user needs to examine the unzipped package, read the docs and identify which files are optional and/or exclusive, if any. You missed a step between slide 2 and 3 in the Advanced Installer Creation. This not only prevents any possible conflicts but also keeps all the related docs files grouped together instead of lost in a sea of other doc files.Ĥ. It's better practice to just use a unique subfolder for each mods documentation as mentioned in #2.
I've never investigated if it does this or not, but I'm quite sure it's mentioned in the Bash docs.
#ALTERNATIVES TO MOPY FISH MOD#
As far as I know, Wrye Bash is supposed to rename any file that is named just Readme.* (txt only maybe) so that the filename will include the mod name.
#ALTERNATIVES TO MOPY FISH INSTALL#
Often the docs are just install instructions, which are of no use once the mod is already installed.ģ. This allows people to opt not to install the docs for a particular mod. If there several doc files, they should go in a subfolder of the docs folder, so they would go in Data/Docs/Mod X/*.* The recommend standard for doc files is to place them in their own sub-package named 00 Docs unless you are making a simple BAIN. In fact, I also have an Add to "XXX.7z" menu item, which bypasses the 7zip window from even coming up.Ģ. I dunno about your version of 7zip or how you have it configured, but I have no problems to zip just folders.