SkyrimLE:Bashed Patch: Difference between revisions
From Step Mods | Change The Game
TechAngel85 (talk | contribs) No edit summary |
TechAngel85 (talk | contribs) No edit summary |
||
| Line 58: | Line 58: | ||
{{MO Note|After closing Wrye Bash and returning to MO, the ''"bashed patch, 0.esp"'' will be located in the ''"Overwrite"'' folder. {{fc|#ddd|(If there is no patch in Overwrite, it is probably due to past use of Wrye Bash outside Mod Organizer, which would have placed the bashed patch in the real Skyrim data folder instead of in Overwrite [http://forum.step-project.com/topic/4530-]).}} A different Bashed Patch can be created for every MO profile, so it is advised to move the Bashed Patch and its data to a separate mod folder. Simply right click the ''"Overwrite"'' folder and select 'Create Mod', then name it. Example is STEP Core Bashed Patch. You will then need to check it to enable it. Each subsequent time you rebuild the patch, you must open Overwrite and drag the new files back to this mod.}} | {{MO Note|After closing Wrye Bash and returning to MO, the ''"bashed patch, 0.esp"'' will be located in the ''"Overwrite"'' folder. {{fc|#ddd|(If there is no patch in Overwrite, it is probably due to past use of Wrye Bash outside Mod Organizer, which would have placed the bashed patch in the real Skyrim data folder instead of in Overwrite [http://forum.step-project.com/topic/4530-]).}} A different Bashed Patch can be created for every MO profile, so it is advised to move the Bashed Patch and its data to a separate mod folder. Simply right click the ''"Overwrite"'' folder and select 'Create Mod', then name it. Example is STEP Core Bashed Patch. You will then need to check it to enable it. Each subsequent time you rebuild the patch, you must open Overwrite and drag the new files back to this mod.}} | ||
{{RelatedVideos| | |||
*{{Video|W1Es06MtAZM|Wrye Bash - Bashed Patch (by GamerPoets)|GamerPoets demonstrates making a Bashed Patch}} | |||
}} | |||
}} | }} | ||
Revision as of 15:48, August 17, 2015
Bashed Patch
by Wrye Bash TeamCR Patch:
{{{core}}}"{{{core}}}" is not recognized as a Boolean (true/false) value.
LW Patch:
{{{landw}}}"{{{landw}}}" is not recognized as a Boolean (true/false) value.
PP Patch:
{{{pp}}}"{{{pp}}}" is not recognized as a Boolean (true/false) value.
ENB Option:
{{{enb}}}"{{{enb}}}" is not recognized as a Boolean (true/false) value.
WARNING
This template is deprecated. Please revise markup to use Template:GallerySimple instead.Guide/Version-Specific Mod Recommendations
| Existing Guides |
|---|
| 2.10.0 |
| 2.2.9 |
| 2.2.9.1 |
| 2.2.9.2 |
Recommendations
To create the Bashed Patch:
- Ensure all your plugins are active in Mod Organizer.
- Launch Wrye Bash via Mod Organizer.
- Right click on "bashed patch, 0.esp", and select "Rebuild Patch".
- At the Deactivate these mods... prompt, click OK.
- Tick the boxes next to "Merge Patches", "Import Names", "Import Stats", "Tweak Settings", and "Leveled Lists".
- Highlight "Tweak Settings", and tick the box next to "Crime: Alarm Distance". Optional: tick the box next to "Timescale".
- Right-click on "Crime: Alarm Distance" and select '1000' and optionally set "Timescale" to a value less than '20' but no less than '10'.
- Next click [Build Patch] at the bottom of the window to construct the patch based on the current plugin list/order
Related Video(s):
