Difference between revisions of "Sharing Mods"
Jump to navigation
Jump to search
imported>Qazaaq |
imported>Qazaaq |
||
Line 1: | Line 1: | ||
This pages covers details of | [[Category:Editor Reference]] | ||
[[Category:Game Files]] | |||
This pages covers details of sharing user created mods. | |||
==How to upload ESM files== | ==How to upload ESM files== | ||
Line 32: | Line 34: | ||
*There is no reason to add [[INI Fragments]] to your archive. The CK will automatically detect and upload a correctly-named ini as part of the package uploaded to Bethesda.net. | *There is no reason to add [[INI Fragments]] to your archive. The CK will automatically detect and upload a correctly-named ini as part of the package uploaded to Bethesda.net. | ||
*For multiplatform uploads you can add "[XB1]" or "[PS4]" to the end of your mod name to tell them apart (the import/export process will tack them on for you) and the game will trim off those specific suffixes if it sees them (so users on those platforms just see the normal mod name). | *For multiplatform uploads you can add "[XB1]" or "[PS4]" to the end of your mod name to tell them apart (the import/export process will tack them on for you) and the game will trim off those specific suffixes if it sees them (so users on those platforms just see the normal mod name). | ||
== See Also == | |||
*[[:Category:Game_Files|Game Files Category]] |
Revision as of 21:19, 17 July 2016
This pages covers details of sharing user created mods.
How to upload ESM files
Rename your esp to esm in Windows. Then open the ESM in the CK without setting any active plugin. Then when you attempt to upload the CK will detect that there is no active plugin and ask if you want to upload a masterfile instead. Pick the ESM from the dropdown and continue as normal.
Platforms
For XBox:
- Make sure loose assets are available (they're going to be converted and packed)
- Load your plugin in the CK as the active plugin
- Tell the CK to upload for XBox.
- Make sure the list contains everything you want, and nothing you don't.
- Export the list once you perfect it so you don't have to fill it out again later
- Hit OK
- Wait for the CK to convert the files and create the two archives (if necessary)
- Fill out the mod information for Beth.net
- Hit export to save out the data you just filled out
- Click upload
For PS4:
- Make sure loose assets are available (they're going to be converted and packed)
- Load your plugin in the CK as the active plugin
- Tell the CK to upload for PS4
- Import the list you made earlier for your XBox version (you did export a list, right?)
- Hit OK
- Wait for the CK to convert the files and create the archives (for now, because PS4 texture conversion is not supported, no texture archive will be made - attempting to make one yourself will crash the game)
- Import the beth.net information you made earlier (you did export it, right?)
- Click upload.
Notes
- The most common cause of crashes before the add files window opens is a bad nif file, due to the CK going through each model referenced in your mod to get a list of textures and materials.
- There is no reason to add INI Fragments to your archive. The CK will automatically detect and upload a correctly-named ini as part of the package uploaded to Bethesda.net.
- For multiplatform uploads you can add "[XB1]" or "[PS4]" to the end of your mod name to tell them apart (the import/export process will tack them on for you) and the game will trim off those specific suffixes if it sees them (so users on those platforms just see the normal mod name).