Difference between revisions of "How To Prep Mod Files Using TES4Files"
imported>MentalElf (Add "more" indicating more directories could be created as output.) |
imported>Lhammonds (Re-corrected suggestions based on notes in talk page.) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 6: | Line 6: | ||
==Steps== | ==Steps== | ||
1. Start TES4Files | 1. Start TES4Files. In this example TES4Files is installed in the Oblivion/Data subdirectory. | ||
2. Choose '''MyMod.esp''' and check '''Fix NIFs''' and click '''Export''' | 2. Choose '''MyMod.esp''' and check '''Fix NIFs''' and click '''Export''' | ||
| Line 12: | Line 12: | ||
3. Once done, click '''OK''' and close TES4Files, the following directory structure will be created: | 3. Once done, click '''OK''' and close TES4Files, the following directory structure will be created: | ||
'''Oblivion\Data | '''Oblivion\Data\MyMod\MyMod_error.txt''' | ||
'''Oblivion\Data | '''Oblivion\Data\MyMod\MyMod_log.txt''' | ||
'''Oblivion\Data | '''Oblivion\Data\MyMod\Data\MyMod.esp''' | ||
'''Oblivion\Data | '''Oblivion\Data\MyMod\Data\Textures\*''' | ||
'''Oblivion\Data | '''Oblivion\Data\MyMod\Data\Meshes\*''' | ||
'''...more... (depends on mod content)...''' | '''...more... (depends on mod content)...''' | ||
4. Check the error.txt file to make sure there are no missing textures and such. | 4. Check the error.txt file to make sure there are no missing textures and such. | ||
5. Copy your readme file to the same folder as your .esp file since it | 5. Copy your readme file ("MyMod Readme.txt") to the same folder as your .esp file since it will not grab that file. It will copy it if named "mymod.txt" but it is not recommended since Oblivion Mod Manager and similar end-user tools expect the "readme" word somewhere in the filename. | ||
6. Examine the mesh, texture and any other folders with a quick glance to make sure you see everything that should be there. | 6. Examine the mesh, texture and any other folders with a quick glance to make sure you see everything that should be there. | ||
'''NOTE''': TES4Files cannot see files that are not referenced in the .esp file such as DistantLOD, | '''NOTE''': TES4Files cannot see files that are not referenced in the .esp file such as DistantLOD, | ||
texture replacers, music files (unless referenced in script), and any | texture replacers, music files (unless referenced in script), and any optional/alternate files | ||
such as alternate EGM files for example. | |||
You'll have to copy those into this folder yourself. | |||
7. Create an archive in the folder that contains the .esp (do not include the data folder and error/log files). Example: | 7. Create an archive in the folder that contains the .esp (do not include the data folder and error/log files). Example: | ||
| Line 34: | Line 34: | ||
'''Oblivion\Data\MyMod\Data\MyMod.7z''' | '''Oblivion\Data\MyMod\Data\MyMod.7z''' | ||
The contents of the archive should look like this: | The contents of the archive should look like this which would allow the end-user to extract directly into Oblivion's Data folder if they wanted: | ||
'''\Meshes\*''' | |||
'''\Textures\*''' | |||
'''\MyMod.esp''' | '''\MyMod.esp''' | ||
'''\MyMod Readme.txt''' | '''\MyMod Readme.txt''' | ||
''' | '''...more... (depends on mod content)...''' | ||
8. Move your archive and readme to your upload area and delete the temporary export folder: | 8. Move your archive and readme to your upload area and delete the temporary export folder: | ||
Latest revision as of 23:05, 30 July 2007
Overview[edit | edit source]
This tutorial will demonstrate how to prepare your mod for archiving and eventual upload to a mod site.
TES4Files which examines the selected .esp file and pulls all associated NIFs, textures found in the NIFs, sounds, etc. and puts it in a sub-folder with the same name as the mod.
Steps[edit | edit source]
1. Start TES4Files. In this example TES4Files is installed in the Oblivion/Data subdirectory.
2. Choose MyMod.esp and check Fix NIFs and click Export
3. Once done, click OK and close TES4Files, the following directory structure will be created:
Oblivion\Data\MyMod\MyMod_error.txt Oblivion\Data\MyMod\MyMod_log.txt Oblivion\Data\MyMod\Data\MyMod.esp Oblivion\Data\MyMod\Data\Textures\* Oblivion\Data\MyMod\Data\Meshes\* ...more... (depends on mod content)...
4. Check the error.txt file to make sure there are no missing textures and such.
5. Copy your readme file ("MyMod Readme.txt") to the same folder as your .esp file since it will not grab that file. It will copy it if named "mymod.txt" but it is not recommended since Oblivion Mod Manager and similar end-user tools expect the "readme" word somewhere in the filename.
6. Examine the mesh, texture and any other folders with a quick glance to make sure you see everything that should be there.
NOTE: TES4Files cannot see files that are not referenced in the .esp file such as DistantLOD, texture replacers, music files (unless referenced in script), and any optional/alternate files such as alternate EGM files for example. You'll have to copy those into this folder yourself.
7. Create an archive in the folder that contains the .esp (do not include the data folder and error/log files). Example:
Oblivion\Data\MyMod\Data\MyMod.7z
The contents of the archive should look like this which would allow the end-user to extract directly into Oblivion's Data folder if they wanted:
\Meshes\* \Textures\* \MyMod.esp \MyMod Readme.txt ...more... (depends on mod content)...
8. Move your archive and readme to your upload area and delete the temporary export folder:
Oblivion\Data\MyMod\*
References[edit | edit source]
Source: LHammonds Web Site Tool Home Page: MentalElf's TES4FILES