Difference between revisions of "Version Control"
→Understanding .ESM master files vs .ESP plug-in files
imported>HaploTR |
imported>HaploTR |
||
| Line 51: | Line 51: | ||
== Understanding . | == Understanding .esp and .esm files == | ||
.esp files are "Bethesda Plugin Data Files" | |||
* This is the standard file type created by the Creation Kit, to save your mod | |||
* It contains all of the asset reference data used in your mod | |||
.esm files are "Bethesda Master Data Files" | |||
* This is the file type you'll see used by DLC | |||
* It contains the same information used by .esp files, but it can have references merged into it | |||
In the context of using version control in the Fallout 4 Creation Kit: | |||
* The .esm master file will be your primary mod file, containing all the level and asset reference data for your mod. When you're ready to distribute your mod, it's the .esm that you'll upload. | |||
* The .esp file will be the file you and your project contributors use locally to make all your changes. After you merge your changes into the .esm file, the .esp won't contain any references | |||
== Creation of your .ESM file == | == Creation of your .ESM file == | ||