Frequently Asked Questions - About the Project
What happens if Bethesda releases a patch for something you already fixed?
Should this happen, then the next available release of the affected unofficial patch will remove the changes we've made - assuming the issue is completely fixed by Bethesda's patch. In cases where they are not completely fixed, we will remove only those portions of our changes that are confirmed to be fixed.
Has the mod been cleaned?
Yes. All of the unofficial patch mods have been cleaned using the latest available version of TES5Edit. You do not need to clean them yourselves.
Do I need to do a clean save when upgrading?
No! When upgrading one of the unofficial patches, you simply need to copy the new files in and overwrite the old ones. NEVER follow advice given by someone to do a "clean save". In Skyrim, there is no such thing. Performing one can lead to corrupting your save, and nobody really wants that.
Is it safe to install the unofficial patch on an existing save?
Yes. All of the unofficial patches come with scripts designed to go over the state of things we've fixed and make sure your save is up to date with those. You can install them at any point during your game, whether you've completed the entire main quest or you just left Helgen for the first time.
Some issues may not be possible to fix retroactively. Those which can't are listed in the version history with an [NR] tag. Only starting a new game will resolve those issues.
Will the mod be released as an ESM file?
As of October 2013, the answer to this is "yes" - but with a catch. The files themselves are what the CK and the game consider "master files" - that is, a file with the ESM flag set on it internally. However, the file extension on them is still set as .esp.
This is what's known in modding as a "false flagged ESP file" which basically just means you won't damage your save by upgrading to the new format but at the same time will gain the various benefits provided by this. Not the least of which is that the game will be more stable and entire classes of engine related issues will no longer be present.
What is this useless .bsl file for?
The .bsl file included with the package is not entirely useless. If you use the archive.exe file shipped by Bethesda to open the .bsa, the .bsl file is necessary to decode it. Without it, all you'll get is garbage.
Have you included the source code to the modified Papyrus scripts?
Yes. All of the modified and added script source code is included in the .bsa. You'll need to unpack the file in order to be able to view them.
What if I want to use something the unofficial patches have provided? Can I do that?
Yes. You are allowed to use any assets contained in the mod: Scripts, meshes, textures, text, etc. You do not need to obtain permission beforehand. In fact, it is strongly encouraged that you check regularly with the unofficial patch and see if you have edited anything with your own mods that might cancel out a fix. If you find that you have, you may feel free to copy whatever is needed in order to retain the fixes.
In fact, with the nature of Papyrus, it is almost critical that you check to see if a script you intend to change has been updated by the project. Papyrus conflicts can result in CTDs, bloated saves, and performance degradation.
If you feel it necessary, you may also use the unofficial patch as a master to your own mod in order to be sure you're not overwriting a fix. It is up to you to inform your users of this, if you wish to use our file as a master for your own.
Do not include the USKP's ESP file in your distribution if you use it as a master. ALWAYS refer your users to our downloads so they can be sure to obtain the proper files.
Am I allowed to modify your fixes and distribute supplemental packages based on that?
No. We do not permit modification of the actual bug fixes. This policy unfortunately had to come about because certain people took it upon themselves to "fix" things in the USKP they thought were broken but were not. This has led to a number of false reports of bugs attributed to our project that these people are actually responsible for causing. Since these folks have refused all meaningful attempts at communication to resolve this, we are making it explicitly clear we do not condone this type of behavior. It has always been the community's understood etiquette that permission to do things like this is required, and it's backed up by copyright law if you really need to go there. Nobody has EVER had standing permission to produce modifies copies of the work this project has done, and it's extremely disappointing that we apparently need to spell this out clearly now.
This is not the same as the previous question though! If in the course of modifying the game you realize you need to incorporate a USKP fix to prevent it getting lost, that's entirely fine and we encourage that.
If you are confused, ask us, don't just assume you can do as you please.
The unofficial patch changed something that conflicts with my mod. Can you fix this?
No, unfortunately not. The unofficial patches are only answerable to Bethesda's updates and to the bugs in the vanilla game. We are not responsible for any problems fixing a bug may cause in your mod, no matter how popular it may be. It would be best to incorporate the fix into your work so as to avoid the issue to begin with.
There can be certain exceptions made in some scenarios, but they will be handled on a case by case basis. If you feel you have grounds for such an exception, make your case on the AFK Mods forum. Do yourself a favor and don't waste your time trying to rally support by getting a bunch of Nexus users to comment about it. Such tactics will be ignored.
Does text edited by the patch show up in English in non-English games?
Yes, it does, unfortunately. At the moment the only viable way to fix this is for translators to manually update the text in the ESP file and issue a translated package in their preferred language. It's a tedious process, but at present the only one available that doesn't risk corrupting the file.
As the state of translation tools progresses, it may become possible in the near future to issue the ESP file in localized format with external string files that can be translated into other languages more easily, thus allowing for the possibility that the mod could be distributed in one location with multiple translation files available.
What is the proper load order for the Unofficial Patches?
As of October 2013, the load order for these mods has changed! They must now be loaded as follows:
Unofficial Skyrim Patch.esp
Unofficial Dawnguard Patch.esp
Unofficial Hearthfire Patch.esp
Unofficial Dragonborn Patch.esp
[Other ESM Files]
Unofficial High Resolution Patch.esp
[Other ESP Files]
For getting load order set with other mods loaded, please use LOOT. It will provide you a solid starting point for everything that you can then tweak as needed.
I'm getting errors when trying to install the version 2.x.x updates using Nexus Mod Manager
If you get the following error:
BOSS_API_ERROR_INVALID_ARGS: Master files must load before other plugins. The mod was not installed.
You need to perform the following steps:
- Uninstall and delete all the Unofficial patches in NMM.
- Exit NMM.
- Launch NMM again.
- Download and install all of the updated Unofficial patches.
- Run BOSS to sort your load order.
Any other errors you get are likely to be problems with NMM itself or some other issue unrelated to the change in archive formats.
I've seen something called the Skyrim Misc Patches Collection (aka USKP_Addon)? What is this? Do I need it? Is it safe?
The mod known as the Skyrim Misc Patches Collection (aka USKP_Addon) is not an approved extension and does not have the support of the Unofficial Patch Project. It's author has decided to make some deeply subjective design changes to the game and has chosen to market in such a way as to make it seem as though our project approves of its existence. We do not. This mod is not only full of subjective game design changes but also contains poorly implemented replacements for several fixes we've already made that in turn generate conflicts in the game and can even lead to save game corruption.
We have on several occasions attempted to contact the author, who has contributed fixes directly into the patches before and has ALSO provided Italian translations. He refused to address the issues, in fact refused to acknowledge our concerns at all and has continued to operate as though nothing is wrong.
You are strongly advised NOT to use this mod as it will be damaging to your game. We will NOT provide support to anyone who is using it in their games.
We will rescind this warning if and ONLY if these issues are resolved. Further details available.
Posted 07 February 2013 - 11:06 PM
Frequently Asked Questions - About the Project
Also tagged with one or more of these keywords: faq, project
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users