-
Notifications
You must be signed in to change notification settings - Fork 0
/
7-tomeofpsymon.html
1925 lines (1908 loc) · 215 KB
/
7-tomeofpsymon.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
---
layout: default
title: Tome of Psymon
---
<h1 class="header1">{{ page.title }}</h1>
<hr>
<h1 class="grhead1">Main Table of Contents</h1>
<div id="tableOfContents" class="grid-toc">
<div class="toc1">
<h2 class="grhead2">General</h2>
<h3 class="grhead3"><a href="index.html">Welcome</a></h3>
<h3 class="grhead3"><a href="10-contribute.html">Contribute: Generate Wiki pages from Text Files</a></h3>
<h2 class="grhead2">Wrye Bash Related</h2>
<h3 class="grhead3"><a href="2-wryebashfeatures.html">Wrye Bash Features</a></h3>
<h3 class="grhead3"><a href="3-wryemashusage.html">Wrye Mash Usage</a></h3>
<h3 class="grhead3"><a href="4-generalusage.html">General Usage</a></h3>
<h3 class="grhead3"><a href="5-advancedusage.html">Advanced Usage</a></h3>
</div>
<div class="toc2">
<h3 class="grhead3"><a href="6-technicalreferences.html">Technical References</a></h3>
<h3 class="grhead3"><a href="8-tomeofalt3rn1ty.html">Tome of Alt3rn1ty</a></h3>
<h2 class="grhead2">Morrowind Related</h2>
<h3 class="grhead3"><a href="9-morrowindandbeyond.html">Morrowind And Beyond</a></h3>
<h3 class="grhead3"><a href="14-testoolghostwheel.html">TES Plugin Tool (TESTool) 1.3 Docs</a></h3>
<h2 class="grhead2">Oblivion Related</h2>
<h3 class="grhead3"><a href="7-tomeofpsymon.html">Tome of Psymon - BAIN Mod Installation Projects</a></h3>
<h3 class="grhead3"><a href="13-oblivionandbeyond.html">Oblivion And Beyond</a></h3>
</div>
</div>
<p class="empty"> </p>
<div>
<!-- Needed, sets the top of the page just before the H1 Title -->
<hr>
<p>Comprehensive instructions for people who like to read</p>
<h1 class="header1" id="OriginalThreads">Original Threads</h1>
<p class="empty"> </p>
<p class="list-1">• <a href="http://forums.bethsoft.com/topic/1084204-bain-mod-installation-projects/" >BAIN Mod Installation Projects</a></p>
<p class="list-1">• <a href="http://forums.bethsoft.com/topic/1159104-nehrim-and-mods-ii/" >Nehrim and Mods II</a></p>
<p class="list-1">• Original author Psymon.</p>
<p class="list-2">• Other then TesAlliance I have not found a way to get ahold of him except the old bethesda forums and I don't think it will send out notifications for personal messages.</p>
<p class="empty"> </p>
<h2 class="header2" id="Contents">Contents</h2>
<p class="list-1">• <a href="#ModInstallingandModManagement">7.1 Mod Installing and Mod Management</a></p>
<p class="list-2">• <a href="#Whythisinformation">7.1.1 Why this information?</a></p>
<p class="list-2">• <a href="#ModInstallationintroduction">7.1.2 Mod Installation introduction</a></p>
<p class="list-2">• <a href="#Whyuseaninstaller">7.1.3 Why use an installer?</a></p>
<p class="list-2">• <a href="#WryeBashDownloadandManuals">7.1.4 Wrye Bash Download and Manuals</a></p>
<p class="list-2">• <a href="#Morelinksregardinginstallertools">7.1.5 More links regarding installer tools</a></p>
<p class="list-1">• <a href="#TheBasicsofBAINandModArchiving">7.2 The Basics of BAIN and Mod Archiving</a></p>
<p class="list-2">• <a href="#BashInstallerBAINtabfunctions">7.2.1 Bash Installer (BAIN) tab functions</a></p>
<p class="list-2">• <a href="#NavigatingtheInstallersTab">7.2.2 Navigating the Installers Tab</a></p>
<p class="list-2">• <a href="#InstallingandUpdatingPackages">7.2.3 Installing and Updating Packages</a></p>
<p class="list-2">• <a href="#Modpackaging">7.2.4 Mod packaging</a></p>
<p class="list-2">• <a href="#RepackagingModsforBAIN">7.2.5 Repackaging Mods for BAIN</a></p>
<p class="list-2">• <a href="#Modmanagementandyourownmodcatalog">7.2.6 Mod management and your own mod catalog:</a></p>
<p class="list-1">• <a href="#ComplexBAINarchives">7.3 Complex BAIN archives</a></p>
<p class="list-2">• <a href="#ExaminingBAINarchives">7.3.1 Examining BAIN archives</a></p>
<p class="list-2">• <a href="#Prosandconsofcombiningmodsintocomplexarchivepackages">7.3.2 Pros and cons of combining mods into complex archive packages</a></p>
<p class="list-2">• <a href="#Repackagingacomplexarchiveexample">7.3.3 Repackaging a complex archive example</a></p>
<p class="list-1">• <a href="#ManagingInstallerPackages">7.4 Managing Installer Packages</a></p>
<p class="list-2">• <a href="#InstallOrder">7.4.1 Install Order</a></p>
<p class="list-2">• <a href="#NamingConventions">7.4.2 Naming Conventions:</a></p>
<p class="list-2">• <a href="#Updatingbestpractices">7.4.3 Updating best practices:</a></p>
<p class="list-1">• <a href="#CreatingYourOwnComplexBAINPackages">7.5 Creating Your Own Complex BAIN Packages</a></p>
<p class="list-2">• <a href="#PlanningYourModArchive">7.5.1 Planning Your Mod Archive</a></p>
<p class="list-2">• <a href="#RationaleforComplexCustomPackages">7.5.2 Rationale for Complex Custom Packages</a></p>
<p class="list-2">• <a href="#ExamplesofVeryComplexCustomBAINPackages">7.5.3 Examples of Very Complex Custom BAIN Packages:</a></p>
<p class="list-2">• <a href="#LODCompilation">7.5.4 LOD Compilation</a></p>
<p class="list-2">• <a href="#SkyReplacersCompilation">7.5.5 Sky Replacers Compilation</a></p>
<p class="list-1">• <a href="#BAINWizardsOMODSandBAINConversionFiles">7.6 BAIN Wizards, OMODS, and BAIN Conversion Files</a></p>
<p class="list-2">• <a href="#BAINReadingOMODconversionfiles">7.6.1 BAIN Reading OMOD conversion files</a></p>
<p class="list-2">• <a href="#BAINconversionfiles">7.6.2 BAIN conversion files</a></p>
<p class="list-1">• <a href="#BAINandOtherGames">7.7 BAIN and Other Games</a></p>
<p class="list-2">• <a href="#Fallout3andFalloutNewVegas">7.7.1 Fallout3 and Fallout New Vegas</a></p>
<p class="list-2">• <a href="#Morrowind">7.7.2 Morrowind</a></p>
<p class="list-1">• <a href="#ManagingBAINwithMultipleInstalls">7.8 Managing BAIN with Multiple Installs</a></p>
<p class="list-2">• <a href="#Waitdidyousaymultipleinstalls">7.8.1 Wait did you say multiple installs?</a></p>
<p class="list-2">• <a href="#mTES4Manager">7.8.2 mTES4Manager</a></p>
<p class="list-2">• <a href="#MultipleOblivionManager">7.8.3 Multiple Oblivion Manager</a></p>
<p class="list-2">• <a href="#ManagingMultipleinstallsandtheproblemofWryeBash">7.8.4 Managing Multiple installs and the problem of Wrye Bash</a></p>
<p class="list-2">• <a href="#OtherMethodsandnotes">7.8.5 Other Methods and notes:</a></p>
<p class="list-2">• <a href="#MultipleInstallsOneWryeBash">7.8.6 Multiple Installs - One Wrye Bash</a></p>
<p class="list-2">• <a href="#Tipforstartinganewinstall">7.8.7 Tip for starting a new install...</a></p>
<p class="list-1">• <a href="#AnopenletterappealingtotheuseofBAINandWryeBashbymodmakers">7.9 An open letter appealing to the use of BAIN and Wrye Bash by mod makers</a></p>
<p class="list-2">• <a href="#ReasonsforutilizingBAIN">7.9.1 Reasons for utilizing BAIN:</a></p>
<p class="list-2">• <a href="#TosummarizetheadvantagesofusingBAINpackagingforyourmods">7.9.2 To summarize the advantages of using BAIN packaging for your mods:</a></p>
<p class="list-1">• <a href="#RelatedTopics">7.10 Related Topics</a></p>
<p class="list-2">• <a href="#WhyuseaBashedPatch">7.10.1 Why use a Bashed Patch?</a></p>
<p class="list-1">• <a href="#OtherBethesdaGameInterestsofMine">7.11 Other Bethesda Game Interests of Mine</a></p>
<p class="list-1">• <a href="#NehrimandMods">7.12 Nehrim and Mods</a></p>
<p class="list-2">• <a href="#Informativethreads">7.12.1 Informative threads:</a></p>
<p class="list-2">• <a href="#InstallChoices">7.12.2 Install Choices</a></p>
<p class="list-2">• <a href="#NehrimGameContents">7.12.3 Nehrim Game Contents</a></p>
<p class="list-2">• <a href="#ArchiveInvalidation">7.12.4 Archive Invalidation</a></p>
<p class="list-2">• <a href="#OblivionModManager">7.12.5 Oblivion Mod Manager</a></p>
<p class="list-2">• <a href="#OblivionScriptExtender">7.12.6 Oblivion Script Extender</a></p>
<p class="list-1">• <a href="#PortingmodsfromObliviontoNehrim">7.13 Porting mods from Oblivion to Nehrim</a></p>
<p class="list-2">• <a href="#Replacers">7.13.1 Replacers:</a></p>
<p class="list-2">• <a href="#Plugins">7.13.2 Plugins:</a></p>
<p class="list-2">• <a href="#Resources1">7.13.3 Resources:</a></p>
<p class="list-2">• <a href="#Considerations">7.13.4 Considerations:</a></p>
<p class="list-2">• <a href="#Optimizations">7.13.5 Optimizations:</a></p>
<p class="list-1">• <a href="#ModsforNehrim">7.14 Mods for Nehrim</a></p>
<p class="list-2">• <a href="#NehrimEnglishfixesandImprovements">7.14.1 Nehrim English fixes and Improvements:</a></p>
<p class="list-2">• <a href="#Leveling">7.14.2 Leveling:</a></p>
<p class="list-2">• <a href="#MenuManagement">7.14.3 Menu Management:</a></p>
<p class="list-2">• <a href="#HUD">7.14.4 HUD:</a></p>
<p class="list-2">• <a href="#Hotkeys">7.14.5 Hotkeys:</a></p>
<p class="list-2">• <a href="#AnnoyanceRemovers">7.14.6 Annoyance Removers:</a></p>
<p class="list-2">• <a href="#Combat">7.14.7 Combat:</a></p>
<p class="list-2">• <a href="#Stealth">7.14.8 Stealth:</a></p>
<p class="list-2">• <a href="#Companions">7.14.9 Companions:</a></p>
<p class="list-2">• <a href="#ImmersionRealism">7.14.10 Immersion-Realism:</a></p>
<p class="list-2">• <a href="#GraphicImprovements">7.14.11 Graphic Improvements:</a></p>
<p class="list-2">• <a href="#EnvironmentsWeather">7.14.12 Environments/Weather:</a></p>
<p class="list-2">• <a href="#Homes">7.14.13 Homes:</a></p>
<p class="list-2">• <a href="#Other">7.14.14 Other:</a></p>
<p class="list-2">• <a href="#OBSEPluginsthatsofarwork">7.14.15 OBSE Plugins that so far work:</a></p>
<p class="list-2">• <a href="#ReplacersTextures">7.14.16 Replacers-Textures:</a></p>
<p class="list-2">• <a href="#TheBashedPatch">7.14.17 The Bashed Patch:</a></p>
<h1 class="header1" id="ModInstallingandModManagement">7.1 - Mod Installing and Mod Management</h1>
<p class="empty"> </p>
<p>The focus of the first post of this thread is to attempt to explain the need for using an installer and BAIN in particular. In the following posts will be explanations of BAIN functions and related topics.</p>
<p class="empty"> </p>
<h2 id="Whythisinformation">7.1.1 - Why this information?</h2>
<p class="empty"> </p>
<p><a href="http://forums.bethsoft.com/topic/957424-custom-bain-projects/" >My original thread</a> on this subject has long since reached its end. My intentions at that time were to mostly have a place to post about how I was using the then new installer created by Wrye and part of the Wrye Bash program. I tend to not like to create threads and usually try to post whatever questions or statements in existing threads. I know when I find something I like I can get a bit zealous about it and, at the time, didn't want to overwhelm other threads with my extremely self-indulgent uses of this new installer. Having it be instructional was really an after-thought. Having gotten the zealous part mostly out of my system I now return to this and hope that this thread, or at least the opening posts will be more instructional and I will do my best to collect and/or link all the best material related to this subject.</p>
<p class="empty"> </p>
<p>I'd like to point out that I am primarily what most would consider a mod-user. [I do not like that term and will explain why below, but for now let me play along.] While I've altered many esp files and even created my own house mod (that will remain unreleased), all the rest I've learned I've picked up from the perspective of a person who uses other, 'real modders', work. Because of this most of what I will attempt to write will be for those who are new to mod using and are trying to get a handle on how to best apply already made mods to their install. Primarily this is being written with TES4: Oblivion in mind, but most of it will and can also apply to TES3: Morrowind and Fallout 3.</p>
<p class="empty"> </p>
<h2 id="ModInstallationintroduction">7.1.2 - Mod Installation introduction</h2>
<p class="empty"> </p>
<p>Let's just start with - "well here we are wanting to mod these Bethesda games." Asking 'How best can I do this?' is not usually where most people start. The way I take it most people start with a game they like then play it for a while maybe do some internet searches and read or hear about these 'unofficial add-ons' called mods and then maybe find a link somewhere to download and then the first learning curve hits with the question 'what is the fastest way I can get this in my game without straining my brain too hard?' Perhaps there is also the thought that 'wow this is complicated', or 'only computer tech people could do this.' If a person is reading this to really learn how to do use mods then they may have an inkling that many consider Bethesda to make some of the most moddable games, promotes modding, and has three of the most modded games on the market.</p>
<p class="empty"> </p>
<p>From this then a person may just dive right in and install these user made mods the old fashion way: manual installing. That means finding out what file needs to go where and then installing it there by copying or cutting from the downloaded content and pasting into the appropriate folder directory of the game install. Doing this, in my opinion, is the most educational way of learning how to add mods. It is by this method that one really has to read the readme and get familiar with all the file directories and the general directory layout and functioning of the game in question.</p>
<p class="empty"> </p>
<p>So with this we learn that the game exe calls upon information from the data directory for the material of what is presented in-game and that where the presented material presents is stored in the save game files often found in another directory. Most modding has to do with adding user made mods to the Data directory. Most of what it takes to do manual installing can be read in the pinned thread called <a href="http://forums.bethsoft.com/topic/449239-oblivion-mods-faq/" >OBLIVION MODS FAQ</a> He does describe the use of installers. This thread will be about the use of installers and specifically BAIN.</p>
<p class="empty"> </p>
<p>So the next phase of most mod users learning curve is after they get in over their head. This is the result of shiny new mods and the very, very deep catalog of mods created for these games. So a user begins by installing some mods to improve graphics, then game settings, then an overhaul is isntalled, but wait that is not the right one ... err maybe that one. Then the game crashes begin - the dreaded ctds: crash to desktops. Then thinking that 'well I guess I should uninstall my game and start over, but next time I will get it right!' Then we are at the original question of how best to do this. Unfortunately, that really is just the beginning because using programs to automate installation means that they are subject to the same rules as all software programs: Junk in = Junk out.</p>
<p class="empty"> </p>
<h2 id="Whyuseaninstaller">7.1.3 - Why use an installer?</h2>
<p class="empty"> </p>
<p>So from this frustration of losing track of all that is installed the need for an automated way to do things is born. Mod Managers are not exclusive to bethesda games and doing a quick google search of the words and you will see many games have mod managers available. Mod Managers automate the installation of user-made-mods (from now on called 'mods'). They are tools whereby the data from a user made mod can be installed and better yet removed with the click of a few buttons. For Oblivion the standard has been <a href="http://timeslip.users.sourceforge.net/" >Oblivion Mod Manager</a> or OBMM for short. <a href="https://www.nexusmods.com/oblivion/mods/2097" >the OBMM download page</a>.</p>
<p class="empty"> </p>
<p>OBMM is a great mod installer. There are a few older ones but as far as a straight away mod installer it is rich with features and by the standards of most light to moderate mod users it will serve the purpose of installing mods very well. It can automate mod installation so that very little thought about what is happening and where things go can blissfully be ignored. All the better that many mods come as either OMODS (packaged to be used by OBMM) or OMOD ready (able to be made into OMODS). There is also a Morrowind Mod Manager, which is primitive, and a very highly developed <a href="https://www.nexusmods.com/newvegas/mods/36901" >Fallout Mod Manager</a>, which is starting to make the Oblivion Mod Manager look as primitive as the Morrowind Mod Manager looks when compared to OBMM. The author, Timeslip, continues to develop the FOMM with the help of Kaburke. Recent Thread found <a href="http://forums.bethsoft.com/topic/1173611-relz-fallout-mod-manager/" >here</a>. And with OBMM scenttree is making additions with <a href="https://www.nexusmods.com/oblivion/mods/32277" >Oblivion Mod Manager Extended</a>, which includes more control in installing loose files.</p>
<p class="empty"> </p>
<p>The issues or problems with OBMM (or the other varieties) is really a matter of perspective. From a mod makers point of view these programs may indeed be heaven sent because with just some tinkering and packaging a very complex mod can be made available for instant download and installation. This cuts down on the number of complaints and inquiries about how to install the uber-mod-to-end-all-mods (... ohh shiny). And for users who only want to use a moderate amount of mods and not think about what is happening under the hood then it is great. On the other hand, those who do wish to see what is happening under the hood or want to use many mods then the Mod Managers start to show their weaknesses and shortcomings.</p>
<p class="empty"> </p>
<p>My critique of the mod manager is not meant to be unfair to it and I will own that it is my own viewpoint. The Morrowind Mod Manager is not nearly developed enough to warrant using as an installer and the FOMM in its current editions includes many features that attempt to address the shortcomings of the OBMM. To summarize my points:</p>
<p class="empty"> </p>
<p class="list-1">• The OBMM does not encourage users to think about file directory or about how a manual install of the same mod would work. This has a net effect of reducing a person who is 'modding their game' down to a mere mod-user. To me that further creates a rift between mod makers as the real modders and mod-users as their customers. The caveat being that yes one can script the OMOD files to install in any fashion whatsoever, but again the effect I've seen this have is encouraging sloppy and confusing packaging of mods.</p>
<p class="empty"> </p>
<p class="list-1">• The OBMM does not offer a comprehensive solution to managing install order, particularly of replacer files. i.e. if one were to want to make sure that a certain replacer was always installing last and was part of larger mod then one would have to uninstall and reinstall said mod. As a caveat there is an option to be notified of conflicts and will even tell you what other OMOD the file comes from and whether you want to overwrite the file in question. This can be very tedious with lots of files to individually click yes/no to.</p>
<p class="empty"> </p>
<p class="list-1">• The OBMM conflict detector is near useless. Unless you've trained yourself to make sense of what it is telling you mostly it is a confusing report.</p>
<p class="empty"> </p>
<p class="list-1">• The OBMM can crash and when it does it will lose records of all installed OMODS and require a reinstall of all of them. The unfortunate part of this is the more OMODS you have installed the more likely that this is to happen. This, ultimately, is what made me want to move onto another installer. After several crashes in a short span of time I was about ready to give up on a modded Oblivon.</p>
<p class="empty"> </p>
<p>In concurrent development there was another utility for these games brought to us by Wrye. This was originally the Wrye Bash program for Oblivion but he also created a Wrye Mash program for Morrowind. Wrye Bash (sometimes shortened to WB) is a multipurpose tool with many many features for modders (mod users and mod makers alike). Here is a short and very incomplete summary of its features:</p>
<section class="quote">
<p class="attr">Quote</p>
<p class="list-1">• An advanced load order tool (adjust and manage load ordering of mods).</p>
<p class="list-1">• A save game managing tool (create profiles, remove same game bloat, etc).</p>
<p class="list-1">• Allow automating of INI edits.</p>
<p class="list-1">• Manage screenshots and archive PM messages from boards such as this one.</p>
<p class="list-1">• Bashed Patch creation (which includes):</p>
<p class="empty"> </p>
<p class="list-1">• Merge leveled list altering mods to reduce conflicts.</p>
<p class="list-1">• Further merge mods and reduce active mods thereby increasing max mods useable.</p>
<p class="list-1">• Import only specific records within mods and further control load order via Bash Tags.</p>
<p class="list-1">• Library of game settings that can be adjusted with each bashed patch building.</p>
</section>
<p>The last portion of Wrye Bash that Wrye worked on before passing the project on to others to manage in his absence is what is known as BAIN which is short for BAsh INstaller. The BAIN component aptly handles the shortcomings of the Oblivion Mod Manager and in my opinion offers features that greatly expand upon the functions of mod installer programs to date. The features that I'd like to point out are:</p>
<p class="empty"> </p>
<section class="quote">
<p class="attr">Quote</p>
<p class="list-1">• BAIN encourages thinking about what a manual install is and how things work 'under the hood.'</p>
<p class="list-1">• BAIN offers minute control of files and gives sensible conflict reports and control options of resolving those conflicts.</p>
<p class="list-1">• BAIN gives us the ability to manage install order - a term analogous to load order with regard to esm/esp files.</p>
<p class="list-1">• BAIN Provides detailed reports of what it installs and can tell you if what was installed has changed, been overwritten, is missing, or even if a file was not installed.</p>
<p class="list-1">• BAIN requires no special OMOD files and can work with 7zip, rar and other common archiving methods (7zip being the recommended though), as well as, regular file folders (projects).</p>
<p class="list-1">• BAIN offers the ability to create your own packages that can include any number of mods with the limit being only what you can manage to create with file directory juggling.</p>
</section>
<p class="empty"> </p>
<p>Most of what this thread will be about is the general uses of the BAIN tab, formatting of BAIN ready packages, and the creation of custom BAIN packages.</p>
<p class="empty"> </p>
<p>Many took my last thread as if I were bashing on OBMM. Not true and the point is that really they each have their strengths. There are things that OBMM can do that Wrye Bash cannot. Some of these include:</p>
<p class="empty"> </p>
<section class="quote">
<p class="attr">Quote</p>
<p class="list-1">• The installation and merging of Shaders. installation of shaders is possible with Bash 291, but not shader merging or editing.</p>
<p class="list-1">• OBMM Will install anything you put into an OMOD and create any directory you create as well. Including other archives and executable files.</p>
<p class="list-1">• Scripted installs that edit the ini automatically and change the name of plugins on install. There are plans to create scripted BAIN wizards - keep checking new bash versions.</p>
<p class="list-1">• BSA management including extraction and the packaging of BSA files.</p>
<p class="list-1">• OBMM handles foriegn language characters on file names (unicode) much better than BAIN can.</p>
</section>
<p class="empty"> </p>
<p><a href="https://en.uesp.net/wiki/Tes4Mod:Bash_vs._OBMM" >More about comparing BAIN and OBMM</a> (though a bit outdated).</p>
<p class="empty"> </p>
<p>In short I use both with about 96% of my install managed through BAIN and the rest via OBMM. So for most replacers, large projects, loose random files, mainstream regularly formatted mods and so on I use BAIN. For OBSE extensions, Shader mods (Night eye shaders), and heavily and elegantly scripted OMODs such as those made by theNiceOne or ABO it is OBMM. The main feature I use on OBMM is drag and drop load ordering.</p>
<p class="empty"> </p>
<p>The advantages I've experienced in moving to BAIN include:</p>
<p class="empty"> </p>
<p class="list-1">• It has kept me grounded in thinking about manual installing and what that implies which has in turn kept me thinking of the this process as modding instead of mod-using.</p>
<p class="list-1">• It has made it so that I never really have to think about uninstalling and reinstalling the game again. In other words I've never again felt overwhelmed by the amount of material installed and never felt as though I could not manage this material.</p>
<p class="list-1">• It has allowed me to manage and catalog an enormous mod collection where I could change my load order in very dramatic and comprehensive ways within a very short time.</p>
<p class="list-1">• It gave me a hobby, some might say an addiction.</p>
<p class="empty"> </p>
<p class="empty"> </p>
<h2 class="header2" id="WryeBashDownloadandManuals">7.1.4 - Wrye Bash Download and Manuals</h2>
<p class="empty"> </p>
<p><a href="https://www.nexusmods.com/oblivion/mods/22368" >Wrye Bash Main download</a></p>
<p class="empty"> </p>
<p><a href="https://wrye-bash.github.io/docs/Wrye%20Bash%20General%20Readme.html" >General Readme</a></p>
<p><a href="https://wrye-bash.github.io/docs/Wrye%20Bash%20Advanced%20Readme.html" >Advanced Readme</a></p>
<p><a href="https://wrye-bash.github.io/docs/Wrye%20Bash%20Technical%20Readme.html" >Technical Readme</a></p>
<p><a href="https://wrye-bash.github.io/docs/Wrye%20Bash%20Version%20History.html" >Version History</a></p>
<p class="empty"> </p>
<p class="note">All 4 sections are listed seperatly because of a lack of smooth navagation between pages</p>
<p class="empty"> </p>
<h2 class="header2" id="Morelinksregardinginstallertools">7.1.5 - More links regarding installer tools</h2>
<p class="empty"> </p>
<p>I'm often told that I'm too wordy, so if you prefer pictures then check out:</p>
<p><a href="https://www.nexusmods.com/oblivion/mods/35230" >Pictorial Guide to Wrye Bash and BAIN by Alt3rn1ty's</a></p>
<p>Perhaps someday these two guides can be merged!</p>
<p class="empty"> </p>
<p>Many a great resource and more Wrye Bash instructions for the mod user:</p>
<p><a href="http://wiki.theassimilationlab.com/tescosi/Main_Page" >TESCosi by Tomlong</a> available in Wiki format. <a href="http://forums.bethsoft.com/topic/1094618-tesivpositive-site-redesign/" >Current forum thread</a>.</p>
<p><a href="http://wryemusings.com/Wrye%20Bash.html" >Wrye Bash Manual</a> very outdated compared to the readme included with the latest download.</p>
<p><a href="https://cs.elderscrolls.com/index.php?title=Wrye_Bash" >Wrye Bash on CS Wiki</a></p>
<p><a href="https://cs.elderscrolls.com/index.php?title=Bain" >BAIN on the CS Wiki</a></p>
<p><a href="http://wryemusings.com/" >Wrye Musings</a> Many Things Wrye ... including wrye views.</p>
<p>The latest <a href="http://forums.bethsoft.com/topic/1191492-relz-wrye-bash-thread-66/" >Original Wrye Bash thread</a> as of this writing. If not current just search the last day or two and you will likely find it. This is where you go for technical help in operating the tool.</p>
<p><font class="red">NOTE:</font> The latest thread for <a href="https://www.afkmods.com/index.php?/topic/4966-wrye-bash-all-games/" >Wrye Bash</a> is on AFK Mods at this time.</p>
<p class="empty"> </p>
<p><a href="https://www.nexusmods.com/oblivion/mods/32277" >Oblivion Mod Manager Alternate Download</a></p>
<p><a href="https://www.nexusmods.com/oblivion/mods/32277" >Oblivion Mod Manager Extended</a> New improvements in graphic interface and presentation as well as scripting.</p>
<p><a href="http://timeslip.users.sourceforge.net/" >OBMM main project page</a></p>
<p><a href="https://hammondslegacy.com/obmm/news.asp" >OBMM instructions</a> - this site contains a lot of information about archive management in general as well.</p>
<p class="list-1">• Originally <a href="http://lhammonds.game-host.org/obmm/default.asp" >http://lhammonds.game-host.org/obmm/default.asp</a> needs verification</p>
<p><a href="https://hammondslegacy.com/obmm/tutorial_create_archive.asp" >OMOD creation tutorial</a></p>
<p><a href="https://cs.elderscrolls.com/index.php?title=How_To_Create_an_OMOD" >OMOD creation on CS Wiki</a></p>
<p class="empty"> </p>
<p><a href="http://forums.bethsoft.com/topic/449239-oblivion-mods-faq/" >Mods general FAQ</a></p>
<p><a href="https://cs.elderscrolls.com/index.php?title=Oblivion_Mods_FAQ" >Mods FAQ on CS Wiki</a></p>
<p><a href="https://cs.elderscrolls.com/index.php?title=Glossary" >Modding Glossary</a></p>
<p><a href="https://cs.elderscrolls.com/index.php?title=Category:Tools" >Tools of mod makers and mod users alike</a></p>
<p class="empty"> </p>
<p>See Post 7: <a href="#BAINandOtherGames" >BAINandOtherGames</a> for information on how to use BAIN for other other games.</p>
<p class="empty"> </p>
<p>And thanks to the modders and utility developers that make playing and modding these games so much fun.</p>
<p class="empty"> </p>
<h1 class="header1" id="TheBasicsofBAINandModArchiving">7.2 - The Basics of BAIN and Mod Archiving</h1>
<p class="empty"> </p>
<h2 class="header2" id="BashInstallerBAINtabfunctions">7.2.1 - Bash Installer (BAIN) tab functions</h2>
<p class="empty"> </p>
<p>To begin with most of what I'm writing is an elaboration of what is in the <a href="#WryeBashDownloadandManuals" >Wrye bash readme</a> (the most current version packaged with the latest Wrye Bash and accessed with ? button on bottom toolbar of Wrye Bash) and I highly suggest you take that as the authority and follow it if I deviate from what is presented there. Next one should direct general questions about the technical problems and functioning in the current Wrye Bash thread. Otherwise if everything is understood and I can answer (or anyone can answer) then ask. I just want to emphasize that those places are a higher authority.</p>
<p class="empty"> </p>
<p>When first installing Wrye Bash (or Wrye Mash or Gary Bash/Wrye Flash) the Installers tab is usually deactivated and when you first click on it you will get a notice asking if you really want to activate the tab. After activating the tab the it will take a few minutes to initialize. It is important do not interrupt this scan because each time you open the tab from this point forward it will scan what you have installed to check if anything has been altered or removed in order to inform you. This is a good thing. The first time you open this may take a few minutes. If you do interrupt the scan then most often you can reopen the tab after restarting Wrye Bash and it will scan again.</p>
<p class="empty"> </p>
<p>This will also create a new directory outside of the main game directory. For Wrye Bash and Gary bash this will be a directory called either Oblivion Mods or Fallout 3 mods and are found right next to the main game directories. Each of these will, in turn, contain a folder called 'Bash Installers.' (There may be a way to alter that so that another drive or directory is used as you can with screenshots.) For Wrye Mash (at this time) the BAIN installers directory is found at the top directory of the game ... Morrowind\installers.</p>
<p class="empty"> </p>
<p>When adding a BAIN friendly archive (called packages once installed) place it in this added directory in the folder called 'Bash Installers'. At each opening of the Installers tab this folder is scanned each package is compared to each other package to the contents of the data folder. The purpose of this is to inform you of changes to what was installed (including if files were altered or missing).</p>
<p class="empty"> </p>
<p>The method by which this is done is <a href="https://en.wikipedia.org/wiki/Cyclic_redundancy_check" >called a cyclic redundancy check</a>. If this check fails then the tab will be blank. A frequent cause of this is moving archives in and out of the bash installers folder while the check is happening, so make sure to add or remove all packages you want to be included in the scan prior to opening or refreshing the the installers tab. If there is another cause for this then please direct the question to the latest Wrye Bash thread and the developers overseeing the latest version.</p>
<p class="empty"> </p>
<h2 class="header2" id="NavigatingtheInstallersTab">7.2.2 - Navigating the Installers Tab</h2>
<p class="empty"> </p>
<p>Firstly read over the <a href="https://wrye-bash.github.io/docs/Wrye%20Bash%20General%20Readme.html#bain-overview" >Installer Tab readme</a> from the Wrye Bash readme (the Readme is always more up to date than this one).</p>
<p class="empty"> </p>
<p>Upon opening the tab one is confronted with 5 panels. Along the entire left side is the package list that looks much like a load order launcher app. If the scan was successful it will contain all the archives added to the Bash Installers folder. Here they are called packages and each has a column describing install order and date modified. The Modified date is of little importance (although it can be informative for telling you when a package was created). the Install Order column though is very helpful in managing your BAIN packages and automating the install order.</p>
<p class="empty"> </p>
<p>Much was made previous to BAIN about the importance of install orders and what mods and their attendant replacers should be installed before (or after) any number of other mods. These concerns are no as of longer of great import with the inherent functionality of BAIN. The install order can now be adjusted without necessarily uninstalling or reinstalling as the management of all files will be handled by BAIN.</p>
<p class="empty"> </p>
<p>Key functions of the installers tab are found with the info-tabs (sub-tabs to the main tab which is the installers tab) that are found at upper right side of the installers tab these include:</p>
<section class="quote">
<p class="attr">Quote</p>
<p class="list-1">• General info-tab: The ability to view the contents of a package prior to installing.</p>
<p class="list-1">• Matched info-tab: The ability to see what in the packages matches what is already installed in the data folder. If two files share the same name but different sizes then that is not a match.</p>
<p class="list-1">• Missing info-tab: The ability to view if anything that was installed from the package has since gone missing.</p>
<p class="list-1">• Mismatched info-tab: will tell you if any files with the same name are actually different in other ways.</p>
<p class="list-1">• Conflicts info-tab: will tell you what other packages are either overwriting the contents of the current package or what packages the current package is overwriting. This is reflected in the designation of higher and lower. If conflicting with manual or OBMM installation then no info is given here, but most likely is given in the other sub-tabs. This tab provides a meaningful conflict detector for replacers that can give valuable information about what your install order should be.</p>
<p class="list-1">• Underridden info-tab: Shows packages which should be overridden, but are not, due to install order errors. This will often give reports after the install order of packages is changed.</p>
<p class="list-1">• Skipped info-tab: will tell you what was not installed. This is likely because it is a file or directory type that is not recognized by BAIN.</p>
</section>
<p class="empty"> </p>
<p>The next two panels are located below these sub-tabs and are content filters:</p>
<section class="quote">
<p class="attr">Quote</p>
<p class="list-1">• A filter for sub-packages: Shows which of the sub-packages are installed (explained later).</p>
<p class="list-1">• A filter for esm/esp: Shows which of the esm or esp are installed and the area where you also decide which (if any) of the plugins or master files you want installed.</p>
</section>
<p class="empty"> </p>
<p>The final pane is a comments pane and it allows you to input comments about each package. Contrary to hopeful thinking it does not present the readme for the package. You ca, however, copy and paste a readme or two into this pane. I use it to write myself little notes like 'Load this package after package so and so.'</p>
<p class="empty"> </p>
<p>The package list can be sorted with Wrye Bash by ctr+arrow keys the packages can also be sorted and new install orders can therefore be automated. This is a leap from what Oblivion Mod Manager offers. For example say you wish to make sure that a certain replacer set ( a clothing texture overhaul for example) was installed last. With each new mod you installed with OBMM you would have to check to make sure it did not overwrite any replacers the replacer set installed and if it did you would have to uninstall the entire replacer set an reinstall over the new mod. With BAIN you can simply move the package you want to win the conflict and adjust just those files with the anneal feature.</p>
<p class="empty"> </p>
<p>Many functions of the BAIN tab are accessed through what are known as context menus. You will notice in the packages panel there is a bar along the top that says obviously enough 'Packages.' Right click on this and a context menu will drop down. Much like with the mods tab you are more likely to find more global commands on the top bar while the context menu accessed through right clicking a package is more likely to be commands for only that package.</p>
<p class="empty"> </p>
<h2 class="header2" id="InstallingandUpdatingPackages">7.2.3 - Installing and Updating Packages</h2>
<p class="empty"> </p>
<p>The packages are installed by right clicking the package to bring up the context menu and clicking install. This will install all the content from the package (or sub-packages you have filtered to install) including replacers, BSA, ESM and ESP files as well as readmes and other commonly found files used in Oblivion modding. You will find as you go on that there are certain files that BAIN will not install:</p>
<p class="empty"> </p>
<p class="list-1">• It will not install exe or executable files.</p>
<p class="list-1">• It will not install archives in a further embedded, zipped/compressed state.</p>
<p class="list-1">• It will install Shaders but it will not merge and edit Shader files.</p>
<p class="list-1">• It will install OBSE plugins But only after prompting you to approve this.</p>
<p class="empty"> </p>
<p>... These are areas where OBMM does outshine BAIN.</p>
<p class="empty"> </p>
<p>If you run across a file that BAIN seems to refuse to install or that you can see will place in a non-usual folder in the data directory (such as data\ini or data\streamline) then with the context menu make sure to check Has Extra Directories if this does not work and the file is not of the non-supported variety above then report that in the latest Wrye Bash thread.</p>
<p class="empty"> </p>
<p>As you learn more about package management and adjust the install order of packages you may notice the package names turning different colors. This is mean to notify you that overwrites and underwrites are happening. Usually you can read the info-tabs for more information. The likely cause is that you have:</p>
<p class="empty"> </p>
<p class="list-1">• Moved another package lower in the load order which now wants to overide a file in the package in question.</p>
<p class="list-1">• Installed an archive that similarly wants to overide a file in the package in question.</p>
<p class="list-1">• Have moved the package in question to override another package and it has not yet installed the files it should be overriding.</p>
<p class="list-1">• You have used another program to replace or remove the same files (at least by name) that the package in question wants to has installed.</p>
<p class="list-1">• You have manually removed or replaced the files that the package in question has installed.</p>
<p class="list-1">• Somehow the file installed has been altered (cleaning a mod can cause this).</p>
<p class="empty"> </p>
<p>The following is quoted directly from the Wrye Bash readme (where it is better illustrated) concerning package shapes, colors and general health:</p>
<p class="empty"> </p>
<section class="quote">
<p class="attr">Quote</p>
<p>Checkmarks</p>
<p class="empty"> </p>
<p class="list-1">• Installed packages will be marked with a "+".</p>
<p class="empty"> </p>
<p>Icon Colors</p>
<p>Icon colors indicate the degree to which the package is synchronized with the Oblivion\Data directory:</p>
<p class="empty"> </p>
<p class="list-1">• <font class="green">Green</font>: Package is fully synced. Note that a package can be green even if it is not "Active". E.g. if you have two identical packages and one is (fully) installed, then it will be green and checked. But the identical package will also be green - since it too is fully synced with the data directory.</p>
<p class="list-1">• <font class="red">Red</font>: Some files in the package are missing from the data directory.</p>
<p class="list-1">• <font class="orange">Orange</font>: All package files are present in the data directory, but some esps/esms are not identical. (E.g. another package installed an alternative version of that file, or the user modified the file after installation.)</p>
<p class="list-1">• <font class="yellow">Yellow</font>: All package files are present in the data directory, but some resource files are not identical. (E.g. another package installed an alternative version of that file, or the user modified the file after installation.)</p>
<p class="list-1">• <font class="white">White</font>: This is relatively rare. It just means that the package is configured in a way that it has no files to install. This can happen for complex packages where none of the sub-packages are checked.</p>
<p class="list-1">• <font class="grey">Grey</font>: This indicates that the package has a structure that Bain does not recognize, and so cannot install.</p>
<p class="list-1">• <font class="red">Red X</font>: The package is corrupt and/or incomplete. You'll likely see this for packages that you are currently downloading into the Installers directory.</p>
<p class="empty"> </p>
<p>Icon Shape</p>
<p class="empty"> </p>
<p class="list-1">• Diamond: A project, i.e. a subdirectory in the Installers directory.</p>
<p class="list-1">• Square: A mod package archive. Note that only rar, 7z and zip formats are supported.</p>
<p class="empty"> </p>
<p>Text Colors</p>
<p class="empty"> </p>
<p class="list-1">• <font class="blue">Blue</font>: Indicates a package with sub-packages. The files to be installed, and thus the install state of the package will depend on which sub-packages you have activated.</p>
<p class="list-1">• <font class="grey">Grey</font>: This indicates that the package has a structure that Bain does not recognize, and so, cannot install.</p>
<p class="empty"> </p>
<p>Text Background</p>
<p class="empty"> </p>
<p class="list-1">• <font class="orange">Orange</font>: Indicates that the install is dirty. This will occur for packages for which the configuration has been altered (either by altering active sub-packages and esmps, or by altering the package itself). This can be repaired by running Anneal or Anneal All.</p>
<p class="list-1">• <font class="yellow">Yellow</font>: Indicates that the package has "underrides" i.e. some of its installed files should be overridden by higher order packages. This may happen after reordering mods that have already been installed. It can be repaired by running Anneal or Anneal All.</p>
<p class="list-1">• <font class="grey">Grey</font>: Indicates that some files present in the package will not be installed. This is usually due to a complex structure that is only partially handled by Bain, but can also be due to having files that Bain refuses to install (exe's, dlls, sub-archives, etc.)</p>
</section>
<p>Annealing is a method whereby you can auto-correct the errors reported in the above described package colors and sub-tabs. Using it will take out conflict losers and replace them with the winners. It will replace files that have been removed by other methods (such as OBMM use or manual alterations. It will also replace files that it determines are different than the one installed. This includes cleaned plugins (which is why I recommend cleaning prior to installing with BAIN as covered below). You can anneal individual packages or using the context menu off of the top packages bar set the installers tab to auto anneal when changes are made. This will work only for files installed via the packages and will not take into account files installed via OBMM or manual. You can also do group anneal of all packages installed</p>
<p class="empty"> </p>
<p>Exercise caution and take notes if using OBMM and BAIN together! For instance if you do want to install a mod via OBMM and the result is that it makes a package turn red because it overwrote the files installed by a package then please remember that annealing that package will remove or change back what OBMM installed. Also my own experience is that setting to auto-anneal is a great option to have set all the time. It will auto-adjust files as you juggle package load order and sub-package options. it will not handle the manual changes or if OBMM is overwriting (but anneal all will).</p>
<p class="empty"> </p>
<p>After you install a package then please keep in mind that you still have to manage the install order of any plugins (including bashing patch and other mod tab functions). If one were to install their entire mod list with BAIN then the need to ever wash it all and install it all again is a thing of the past. With a few clicks you can install many mods or remove many mods and it will keep track of everything for you. No more hunting through directories looking for those obtusely named repalcers that you manually installed and thought was great but that now drag your performance down. No more trying to remember what the last OMOD you installed was. With BAIN it is all tracked for you and conflcits reports are given in dynamic, immediate, and user friendly format.</p>
<p class="empty"> </p>
<p>As for reinstalling your entire install. One can either pick to tackle changing each package over or do them all at once - it really doesn't matter because the more you transfer to BAIN the more it will provide better information about your install. Before getting into creating packages let's first examine how mods are packaged.</p>
<p class="empty"> </p>
<h2 class="header2" id="Modpackaging">7.2.4 - Mod packaging</h2>
<p class="empty"> </p>
<p>Most mods that one were to download today are packaged using an archiving program called 7zip it is free, versatile, and powerful. It can also handle other types of archives such as rar files, which are the runner up format for the most common archives you will download. I recommend grabbing that program for both extracting the archives you download and repackaging archives that you will make.</p>
<p class="empty"> </p>
<p>Protocols for packaging mods and the standards of how a mod should be installed vary greatly and it took me some time to make sense of all the variations. For a while it made no sense. It seemed that mod makers and packagers were all randomly just packaging material without rhyme or reason. Over some time I quickly recognized that there was a logic and this usually betrayed the point of view of the mod maker with regard to how they installed mods, their familiarity with installer programs, and their expectations of mod users.</p>
<p class="empty"> </p>
<p>Archives will remain after what is in them is extracted. Sometimes they are packaged in such a way as to easily be categorized as either 'installer friendly' or 'installer unfriendly.' By installer I mean the automated tools such as OBMM or BAIN. Being installer friendly means usually that the archive is packaged in such a way as to be almost immediately useable with OBMM or BAIN. Uninstaller friendly usually means that an installer program would not be able to automatically utilize the archive and therefore they must be repackaged in order to be used by these installer programs.</p>
<p class="empty"> </p>
<p>The installer friendly format is one that contains a directory (or file) tree that matches the directory tree of your game installation. Here is the file tree of my game installation:</p>
<p class="empty"> </p>
<pre>
Games\Oblivion
│
├[Data]
│ ├[Bash Patches]
│ ├[DistantLOD]
│ ├[Docs]
│ ├[Extras]
│ ├[Fonts]
│ ├[ini]
│ ├[INI Tweaks]
│ ├[menus]
│ ├[meshes]
│ ├[Music]
│ ├[OBSE]
│ ├[Sound]
│ ├[Streamline]
│ ├[Textures]
│ ├[trees]
│ ├[Video]
│ │
│ └[The ESM, ESP and BSA files]
├[lex]
├[Mopy]
├[obmm]
├[src]
│
└[the main game directory where the .exe and other tools are often found]
</pre>
<p class="empty"> </p>
<p>This is from a heavily modded game so I reduced the list down to the essentials you will see if you have moderate amount of mods, OBSE, OBMM and Wrye Bash installed.</p>
<p class="empty"> </p>
<p>Having an archive that matches the file tree above means that once extracted at the appropriate directory (data) all the files then go where they are supposed to and the mod is installed. If there is no plugin then the installation is complete and if there is then arranging load order activating it is all that is left.</p>
<p class="empty"> </p>
<p>To do this an archive needs to be packaged at the level of the data folder and the first folders you should see (if there are replacers involved) is the folders directly under the data folder. Many mods are packaged this way and this is very handy for installing manually. This also is the ideal packaging needed for transforming packages into OMODs or direct plugging into BAIN. These are BAIN ready archives (also called BAIN friendly). Of note OBMM can recognize package archives one level higher at the game directory.</p>
<p class="empty"> </p>
<p>But many archives are not packaged like this. Older mods and even today many Morrowind mods generally are packaged in such a way as to necessitate unpackaging into a temporary folder then cutting and pasting files into the proper order. This is BAIN unfriendly. With regard to these patterns of packaging I think I've seen all variety. Examples include having all the optional esp in the main top directory of the archive while the replacers are tucked away in an obtusely named folder or screenshots galore in the main or top folder while the esp files are likewise tucked away in folder structures that could never match game directory (or common sense). Male body mods are the most obtuse and mod-user unfriendly packages. These often include the actual meshes and textures renamed in extra folder not even accessed by the plugins themselves or just left loose where the main replacers are also at.</p>
<p class="empty"> </p>
<p>So for the purpose of brevity your basic BAIN friendly archive should look like this when unzipped:</p>
<p class="empty"> </p>
<p>Mod of Awesomeness:</p>
<pre>
├[meshes]
├[Sound]
├[Textures]
└[The ESM, ESP and BSA files]
</pre>
<p class="empty"> </p>
<p>This is also the basic structure of BAIN (and OMOD) packaging. This means the extracted material matches this pattern you are golden. You do not want the result to be that when you extract a package the first folder you see is 'data'. That may be acceptable for manual installing (or OBMM if the OMOD is scripted rightly to take that into account) but not ideal for use with this installer program. Further, it is worth checking all the lower order folders and directories for misplaced files. I've found meshes in texture folders, textures in the wrong texture folder, screenshots and other errata mixed in with the replacers. Usually it is best to double check. You will develop a quick eye for it.</p>
<p class="empty"> </p>
<h2 class="header2" id="RepackagingModsforBAIN">7.2.5 - Repackaging Mods for BAIN</h2>
<p class="empty"> </p>
<p>There are pros and cons to consider when it comes to whether or not to repackage. Usually people will become involved in repackaging simply because an archive is not BAIN friendly. There are other reasons for doing this:</p>
<p class="empty"> </p>
<p class="list-1">• To make sure the readme is installed in a more organized manner and not swept into the docs folder generically named and unorganized. BAIN has a function where it will sweep the readme into the docs folder and if not called readme will add that extension to the title. This can be problematic if many readme files are simply named readme (many overwrites) and with many mods the docs folder could quickly be overfull with misnamed and uncategorized readme docs.</p>
<p class="list-1">• You may want to perform basic edits on a plugin such as adjust the date to effect load order or complex edits or mergers with other plugins.</p>
<p class="list-1">• You may want to combine archives into one archive and create what are called complex packages. This could include making available to install options in the main mod that are not normally installed such as alternate version esp. More will be expalined about this in the next post.</p>
<p class="list-1">• You may want to clean the plugins.</p>
<p class="list-1">• You may want to optimize the meshes. PyFFI Optimized offers the information you will need for that</p>
<p class="list-1">• You may want to clean the plugins (highly recommended):</p>
<p class="empty"> </p>
<p class="empty"> </p>
<p class="list-1">• For Morrowind there is testool - more info found here</p>
<p class="list-1">• For Oblivion and Fallout 3 there is the same edit program created by Elminster called either tes4edit or FO3edit. Depending upon how you name the exe. The latest version found here.</p>
<p class="empty"> </p>
<p>Information on cleaning Oblivion or any plugin:</p>
<p><a href="https://tes5edit.github.io/docs/5-mod-cleaning-and-error-checking.html#ModCleaningProcess" >xEdit Documentation</a></p>
<p class="empty"> </p>
<p>Please keep in mind that cleaning mods is a complex subject and that while these tutorials give very clear steps how to use TES4/FO3edit to automate cleaning it is also ideal to read the readme (and comments on the download site) and possibly bring the existence of dirty edits to the attention of the mod maker. Of course many mods are no longer supported. To be very brief do not clean the unofficial patches, overhauls, esp that have other esp as masters, or esm files. Even if you did run the automated program it may find bad edits (the dirt) but they may be intentional and needed. The best bet if your are not sure is to ask the mod maker or barring that ask on a forum release thread.</p>
<p class="empty"> </p>
<p>From my experience of cleaning 100s if not upwards of over a 1000 mods the most common dirty edits are cell and worldspace that result in moving things by accident and other common CS events like just deleting that tree, so as usual I find the most dirty mods are house and building additions, Landscape (other than UL mods ... ), and quest mods.</p>
<p class="empty"> </p>
<p>The most recommended method for repackaging is to rezip or recompress the mods into new archives. One could also place them into simple file directories within the installers directory which would then be recognized as a project; however, doing this may result in the scanning that occurs skipping the project (simple file directory) and therefore missing any changes applied to that project. Waruddar has posted <a href="http://forums.bethsoft.com/topic/1081915-relz-wrye-bash/" >a more technical explanation</a>. Projects are more ideal for mod making and or other editing projects but not for finished projects and or your own mod catalog.</p>
<p class="empty"> </p>
<p>There is also a rationale for not repackaging archives and that is that BAIN has a feature where if the archive were downloaded from TESNexus or TESAlliance and has the ending file designation (each file at these sights has a unique file extension) then using the archives context menu you have an option to open the download page from these sites in your web browser. This can be very handy when checking for updates to mods.</p>
<p class="empty"> </p>
<p>A workaround for this issue is to simply append those file numbers to the end of whatever custom BAIN package you make. The problem with this, however, is that you can only append one file extention number per package so complex archives with may mods would only get one. I tested this with my custom package of Castle Ravenpride and the package is named like this: CastleRavenpride-BAIN-11999.7z</p>
<p class="empty"> </p>
<h2 class="header2" id="Modmanagementandyourownmodcatalog">7.2.6 - Mod management and your own mod catalog:</h2>
<p class="empty"> </p>
<p>If you have collected even a moderate amount of mods you may find yourself confronted with a few choices. Do you keep the archives you downloaded after installing the mods either manually or with an installer? Do you back them up multiple times?</p>
<p class="empty"> </p>
<p>Why keep a mod archive even if it is not the archive you use to install the mod in the final analysis? Well there are a few reasons I do this. One being that you never know if a mod website like Nexus is going to go down (knock on wood that does not happen). Another reason being that more than a few times I've suddenly found that a modder had decided to pull their mods and these mods are therefore no longer available ... period. Other reasons could include:</p>
<p class="empty"> </p>
<p class="list-1">• The length of time it takes to download may be so long that it is better to store them than wait for that again.</p>
<p class="list-1">• The archives serve as source material and so if you make a mistake repackaging then you readily have the source to fall back on for reference and material.</p>
<p class="empty"> </p>
<p>Even these reasons are going to be mitigated by one overriding factor - disc space. If you have less space then active packages and mods are, of course, going to take precedence over archived and unused mods. Basically keeping archives is a sure way to at the most double the amount of space this project will take. External drives and other storage options are, of course, to be considered.</p>
<p class="empty"> </p>
<p>If one were to opt to repackage archives into another package then using 7zip (linked above) is the best option. A few things to consider with this option. Each update of a mod would mean unzipping the original, doing whatever is necessary like cleaning the plugins, repackaging the archive and then placing that archive in the installers directory.</p>
<p class="empty"> </p>
<p>At each step you would then decide things such as whether to save the original archive or delete it, or whether to copy and paste or cut and paste the new package into the installers directory. Doing things this way one could then have backups of not only the original archives but also the file directories of the new repackaged archives. A smarter move yet is to manage the repackaging and storage on a separate drive from the drive where the game and installers directory is located. In the unfortunate event of drive failure you would have a back up in one place or another.</p>
<p class="empty"> </p>
<p>This was the option I chose for my oblivion install and it consumed enormous amounts of disc space. I have another drive where it is filled with directories where the extracted and recombined archives are laid out ready to be rezipped. I often combine mods into complex packages so if one small esp is updated then I'd unzip it into a folder then rezip the entire package up and copy it to the installers directory. This has resulted in about 3 times the necessary space being used. I will cover best practices for updating packages that will explain how I have the directories backed up in post 5 below.</p>
<p class="empty"> </p>
<p>What follows are links I'd highly recommend reading if you are thinking of a complete reinstall and transition to BAIN:</p>
<p class="empty"> </p>
<p>Tomlong75210's helpful site <a href="http://wiki.theassimilationlab.com/tescosi/Main_Page" >TESCosi by Tomlong</a> this site is growing with good information.</p>
<p>There is a section on <a href="http://wiki.theassimilationlab.com/tescosi/Wrye_Bash#BAIN_Installation" >BAIN Installation of Modded Oblivion</a> that promises to be very helpful.</p>
<p><a href="https://en.uesp.net/wiki/Oblivion:Technical_Support" >UESP Tech Support</a></p>
<p><a href="http://forums.bethsoft.com/topic/1119325-50steps-to-stable-fcom/" >50_Steps To CTD (Almost) Free FCOM+++ Game</a> (good advice even if not installing FCOM)</p>
<p><a href="http://forums.bethsoft.com/topic/762701-windows-vista-performance-guide/" >Windows Vista Performance Guide</a> For those installing on a Windows7 or Vista Platform and have UAC concerns: The basic instructions are to install these games outside of default locations and thereby circumventing the need for elevated privileges.</p>
<p><a href="http://forums.bethsoft.com/topic/881204-the-oblivion-performance-project-topp/" >The Oblivion Performance Project</a> (some outdated information use with caution, but some gold too).</p>
<p><a href="http://forums.bethsoft.com/topic/1172342-relzwipzpyffi-python-file-format-interface/" >PyFFI and other optimizations</a> and <a href="http://forums.bethsoft.com/topic/1172029-relz-oblivion-pyffi-optimization-kit/" >A new PyFFI tool</a> by Ulrim.</p>
<p class="empty"> </p>
<p>For more information about mod conflicts please read this pinned thread: <a href="http://forums.bethsoft.com/topic/775917-compatibility-and-you/" >Compatibility and you</a></p>
<p class="empty"> </p>
<p>Examples that Wrye made to illustrate how to package mods in order to be BAIN friendly: [https://www.nexusmods.com/oblivion/mods/22170 | BAIN Mods]] and again in his <a href="http://forums.bethsoft.com/topic/952489-relz-bain-for-mash/" >BAIN for Wrye Mash thread</a> he gives a lot of advice on best practices. The <a href="https://cs.elderscrolls.com/index.php?title=Bain" >BAIN CS Wiki</a> page was also largely written by Wrye.</p>
<p class="empty"> </p>
<p>The best advice managing install orders: Read the Readme!! Next, Use <a href="https://github.com/boss-developers/boss/releases/tag/v2.3.0" >BOSS</a> - both of these overlooked approaches can also give information on how to organize packages.</p>
<p class="empty"> </p>
<h1 class="header1" id="ComplexBAINarchives">7.3 - Complex BAIN archives</h1>
<p>Approaching the ability to make ... Custom BAIN Projects.</p>
<p class="empty"> </p>
<p>By now one should be familiar with the game directory pattern, how mods are often packaged and how to examine mod packaging, What installers do and in particular how the Wrye Bash installers tab operates. Spend some time getting familiar with these ideas and steps and before you know it you will be skipping over the first two posts annoyed by the noobish instructions in no time. This post is really what most of <a href="http://forums.bethsoft.com/topic/957424-custom-bain-projects/" >this thread</a> was all about.</p>
<p class="empty"> </p>
<h2 class="header2" id="ExaminingBAINarchives">7.3.1 - Examining BAIN archives</h2>
<p class="empty"> </p>
<p>BAIN has a feature that really expands upon what an installer does and what the currently available versions of OBMM cannot do. This is the ability to combine packages (of mods) together in novel combinations. With this feature one could then combine mods together in such a way as to make each addition an option that can be installed or not. Really the only thing limiting the combinations is that the packages are read in a hierarchical manner and one's own imagination about how to combine or break apart archives into sub-packages. Since BAIN (like OBMM) can read one layer further into a packages directory to find the recognized structure of the data directory one can then add other directories that have the similar structure.Taking our Mod of Awesomeness example above one could then assign an alpha-numeric prefix to each sub-package then as long as each new sub-package has such a prefix then it will be recognized by BAIN and the alpha-numeric ordering will then be the order by which these packages will be installed. The reason for Alpha-Numeric is explained by PacificMorrowind:</p>
<p class="empty"> </p>
<pre>
the reason is that in computers (at least generally and is certainly the standard in UIs) numbers are sorted before letters... same as underscores etc. (ie like in Windows Explorer defaults sort is <underbar and similar chars><digits><letters>)
</pre>
<p class="empty"> </p>
<p>So, with the lower numbers/letters being installed first (being higher in the install order) and the higher number/letters being installed last (being lower in the install order). This basically allows for micro install order options to be embedded in larger packages.</p>
<p class="empty"> </p>
<pre>
Mods of Awesomeness-BAIN
├[00 Mod of Awesomeness Core]
│ ├[Docs]
│ │ └[Quests]
│ │ └MoA_Readme
│ ├[Meshes]
│ ├[Music]
│ ├[Sound]
│ ├[Textures]
│ └Mod of Awesomeness.esm
│ └Mod of Awesomeness.esp
├[10 Mod of Awesomeness Part 2]
│ ├[Docs]
│ │ └[Quests]
│ │ └ MoA-2_Readme
│ ├[Meshes]
│ ├[Music]
│ ├[Sound]
│ ├[Textures]
│ └Mod of Awesomeness part 2.esp
</pre>
<p class="empty"> </p>
<p>The adding of the BAIN suffix is not really necessary it is one method by which you can track what packages you create as opposed to the ones made by others or it can be used to signify that the package is BAIN ready. Notice I make further directories for the readme which makes them much easier to find. MoA part 2 could easily be an alternate version and so if the esp are named the same then the second loading version would win the conflict and if all the replacer meshes and textures are identical then there would be no need to package them twice and the second sub package could contain only what is different from the core package. These sub-packages will show up in the sub-packages filter and you then have them as options to install.</p>
<p class="empty"> </p>
<h2 class="header2" id="Prosandconsofcombiningmodsintocomplexarchivepackages">7.3.2 - Pros and cons of combining mods into complex archive packages</h2>
<p class="empty"> </p>
<p>The advantages to this are numerous. The primary advantage that it provides is that you can reduce the amount of packages in the installers directory and this makes viewing and organizing then easier. Other advantages include:</p>
<p class="empty"> </p>
<p class="list-1">• Combine similar mod archives together for central access.</p>
<p class="list-1">• Combine related mod archives together for central access.</p>
<p class="list-1">• Combine many disparate yet miniscule mods together instead of having your install order cluttered by packages as simple as a set of three replacers for repair hammers.</p>
<p class="list-1">• Combine variations on mods in such a way that one could have the core aspects available and many other versions available with the ability to have immediate implementation.</p>
<p class="list-1">• Combine whatever you like.</p>
<p class="empty"> </p>
<p>Disadvantages include:</p>
<p class="empty"> </p>
<p class="list-1">• The sub-tabs that keep track of various installed yet separate packages will not read the differences between sub-packages of the same package. It will see all the data contained as one package. The good news is that when comparing to other packages it will only take into account what is installed from each package.</p>
<p class="list-1">• It is up to the user to make sure that the packages are packed rightly and that they do not inherently conflict in a manner not intended or wanted.</p>
<p class="list-1">• If updating any portion is necessary then rezipping/repackaging the entire package is also necessary.</p>
<p class="list-1">• Perhaps forgetting what you packaged?</p>
<p class="empty"> </p>
<p>For myself the advantages far outweigh the disadvantages.</p>
<p class="empty"> </p>
<p>Taking a real world example of the available weather overhaul called All Natural (note it currently has a fix file available but usually not and it is closing to a more complete version one). Extracting the package we see that it is a complex BAIN package:</p>
<p class="empty"> </p>
<pre>
All Natural-18305.7z
├ -- Screenshots
├[00 Core]
├[01 Real Lights]
├[02 Bash Filter For Various Mods]
├[03 Nascosto Isles Weather Patch]
├[04 Kvatch Rebuilt Patch]
├[05 Oblivifall - Losing My Religion Patch]
├[06 MMM Patch]
├omod conversion data
├All Natural Readme.rtf
├Wizard.txt
</pre>
<p class="empty"> </p>
<p>Upon further examination we can see that the individual packages are laid out following commonly adopted rules of BAIN packaging. The mandatory files are in the 00 sub-package. The optional files are in subsequent packages. Also the authors have included extra content of a Wrye Bash filter for use in importing weather sounds to mod added interiors and patches for the mods Nascosto Isles and Kvatch Rebuilt. This is great as it cuts down on other packages just for those patches and extra content. Also of note is the fact that this mod is actually packaged as a <a href="https://cs.elderscrolls.com/index.php?title=Bain#Triple_.28Bain.2FOBMM.2FManual.29_Archives" >triple compliant BAIN package</a> - notice that there is a folder called omod conversion data. What this means is that the package is also ready to be converted into an OMOD for use with OBMM. This means that the OMOD script will seek out the data from the given folders for installing based upon the choices given in the OMOD installation. This is one of the very advanced BAIN ready mods available (and the best weather mod imo). Also note that the twoo hash marks in front of the screenshots folder mean that this sub-package folder will not even be seen by BAIN so you don't have to worry about your data folder being cluttered with screenshots on a mod you already decided was cool.</p>
<p class="empty"> </p>
<h2 class="header2" id="Repackagingacomplexarchiveexample">7.3.3 - Repackaging a complex archive example</h2>
<p class="empty"> </p>
<p>Taking the above information and considerations we could do this ourselves with existing mods. To illustrate this I will share my repackaging of the quest mod <a href="https://www.nexusmods.com/oblivion/mods/21816" >Et in Arkay in Ego</a> I repackaged the mod and combined it with various available patches like so:</p>
<p class="empty"> </p>
<pre>
Et in Arkay Ego-BAIN
├[00 Et in Arkay Ego Core]
│ ├[Docs]
│ │ └[Quests]
│ │ └EiAmod V1-1_Readme
│ ├[Meshes]
│ ├[Music]
│ ├[Sound]
│ ├[Textures]
│ └EiAmod.esp
├[10 Spiritus Version] - contains only the portions necessary for this au natural version
│ ├[Docs]
│ │ └[Quests]
│ │ └EiAmod V1-1 (spiritus)_Readme
│ ├[Meshes]
│ ├[Textures]
│ ├EiAmod.esp
│ ├MaleBodyReplacerV3.esp
│ └TFF_FantasyFigures_Base.esp
├[20 Shivering Isles Patch]
│ ├[Docs]
│ │ └[Quests]
│ │ └EiAmod_ShiveringIsles_Readme
│ └EiAmod_ShiveringIsles
├[25 Choices and Consequences Patch]
│ ├[Docs]
│ │ └[Quests]
│ │ └EiAmod_ChoicesandConsequences_Readme
│ └EiAmod_ChoicesandConsequences.esp
├[30 [EiA delayer] - this is an alternate delayer found here: https://www.nexusmods.com/oblivion/mods/25859
│ ├[Docs]
│ │ └[Quests]
│ │ └EiAmod_Knights_readme
│ └EiAmod_Knights.esp
├[30 KotN Patch] - this original delays the mod till after the completion of KoN available only from authors.
│ ├[Docs]
│ │ └[Quests]
│ │ └EiAmod_Knights_readme
│ └EiAmod_Knights.esp
├[35 [TOTF Patch]: https://www.nexusmods.com/oblivion/mods/24624
│ ├[Docs]
│ │ └[Quests]
│ │ └EiA+TOTF Patch_readme
│ └TOTF-EiAE Patch.esp
├[50 [UL Patches]: https://www.nexusmods.com/oblivion/mods/13834
│ ├[Docs]
│ │ └[Unique Landscapes]
│ │ └EtinArkay-UniqueLandscapes patches Readme
│ ├EtInArkay-BravilBarrowfields patch.esp
│ ├EtInArkay-CheydinhalFalls patch.esp
│ └EtInArkay-ColovianHighlands patch.esp
├[50 UL Patches Merged] - made by myself using the above as sources.
│ ├[Docs]
│ │ └[Unique Landscapes]
│ │ └EtinArkay-UniqueLandscapes patches Readme
│ └EtInArkay-UniqueLandscapes Merged patch.esp
</pre>
<p class="empty"> </p>
<p>With this all in one package you will see several features. The core package number 00 to make sure it is always at the top contains all the main replacers needed. The next sub=package contains an esp that would overwrite the esp in the core sub-package if chosen. It also contains supplementary body replacer material for use with that version (although probably best to use other updated body replacers and only the esp here). The next two subpackages are available at the main download page and are to be used only if SI or C&C are also loaded. There are two numbered 30 sub-packages this is a method of saying that the choice is either/or and that one should not install both. The first one is part of another package of quest delayers made by statttis and the second one is (or was) available only by request from the authors. Since I would not want both installed they got the same number sub-package. The next package is another patch made by somebodys_kid for the mod <a href="https://www.nexusmods.com/oblivion/mods/11598" >Tears of the Fiend</a>. The next sub-package is a the collected Unique Landscapes patches made by Vorians. And the final sub-package was a merger of the UL patches that is packaged with the other UL patches. It is likewise number the same as the UL patches to indicate that it should not be installed along with the normal UL patches. Notice also, as above, I took renaming the readme into my own hands and added further directories to the docs folder to better organize the ever growing library of readmes (you know ... those things we read after all else fails</p>
<p class="empty"> </p>
<p>This package therefore contains several examples of the benefits and some of the rules necessary for constructing complex BAIN packages/projects. Later in other posts I will illustrate much more elaborate combinations of mods.</p>
<p class="empty"> </p>
<p>You will find as you go on that there are certain files that BAIN will not install:</p>
<p class="empty"> </p>
<p class="list-1">• It will not install exe files.</p>
<p class="list-1">• It will not install archives in a further embedded, zipped/compressed state.</p>
<p class="list-1">• It will not install or more importantly merge and manage Shader files.</p>
<p class="empty"> </p>
<p>... this is where OBMM performs very well.</p>
<p class="empty"> </p>
<p>If the package contains all the normal types of files that are found in 95% of all mods then there should be no issue as long as it is formatted appropriately. Sometimes, though, a package or mod will require a unique folder to be installed under the data directory folder and it will appear that BAIN is refusing to install it. this is most likely remedied though the installer context menu. Find the problem package and right click on it a context menu will appear and then choose the option 'has extra directories.' In most cases this should resolve the issue.</p>
<p class="empty"> </p>
<p>The context menu has other options as well. Please read the <a href="http://wryemusings.com/Wrye%20Bash.html#Overview" >Wrye Bash readme</a> (the most current version packaged with the latest Wrye Bash and accessed with ? button on bottom toolbar of Wrye Bash) for more information. Remember that each package has a context window and the top bar if the package window has a different bar with some global options available for further filtering and package control:</p>
<p class="empty"> </p>
<p>The single most important thing to learn is package colors which indicate the health and status of a package and thereby queue one to read the sub-tabs for more information. After adding and moving packages the most common command you will use is anneal to correct the install of various data files. Just moving packages around in the install order will not automatically remove or add data files one must use the anneal command for that to happen. There is a global auto-anneal feature on the top context menu, but I've still seen examples where it did not kick in and so recommend annealing individual packages anytime you see yellow, red, or orange. These colors may not go away as one package may override due to being at a lower position, but there may be parts that should still be annealed and can be annealed.</p>
<p class="empty"> </p>
<p>Read the Readme!! and Use <a href="https://github.com/boss-developers/boss/releases/tag/v2.3.0" >BOSS</a> - both of the overlooked approaches can also give information on how to organize packages and sub-packages.</p>
<p class="empty"> </p>
<h1 class="header1" id="ManagingInstallerPackages">7.4 - Managing Installer Packages</h1>
<p class="empty"> </p>
<h2 class="header2" id="InstallOrder">7.4.1 - Install Order</h2>
<p class="empty"> </p>
<p>Install order is an important part of planning a modded game of Oblivion. Install order is different from what is commonly called load order because it deals with the entire mod including any replacer files (which could include meshes , textures, and sounds) or extra files (added meshes , textures, sounds, or any other number of files). Load order is about how the game reads the instructions from the esm and esp to run the game engine; whereas, install order is about what files are in place to be referenced by the game engine.</p>
<p class="empty"> </p>
<p>There are several factors to consider. Many mods may attempt to replace the same files or even add variants of the same extra file. It is important to remain aware of this and it is especially salient with meshes and textures as they can have a symbiotic relationship (certain meshes require certain textures). Another important variant of this is LandscapeLOD meshes and textures. Another common consideration is that there are often base replacers which you want in place but that are OK to overwrite by other replacers or the base replacers may contain more files while the other replacer only handles a few variants. From this then a logic about install orders has been promoted. Some of the mods though are considered essential (and that is often debatable as well), and some of the mods are considered elective.</p>
<p class="empty"> </p>
<p>This concern for maintaining install order integrity takes on varying levels of difficulty depending upon the method of installation. Basically better tools give better ease. With manual install it is you that will have to track everything. With OBMM then it is you who will have to track everything, but OBMM automates a lot of the work. BAIN offers dynamic, in the moment, conflict reports and the ability to move BAIN packages around in the install order much like esm and esp are shifted around in the load order.</p>
<p class="empty"> </p>
<p>If we look at BOSS master list we also see several categories categories for load ordering which I've reduced down to this more general list:</p>
<p class="empty"> </p>
<pre>
Earliest mods
NPC face mods
UOP & Vanilla fixes
BSA tricks
Overhauls I - Initial Fran's files for FCOM
Loading Screen Alternatives
Weather mods and overhauls
Sound mods
Lighting
General Base Mods
Map marker Tweaks
Hotkeys
DLC group
Body replacers
Items (armor and weapons)
Body Replacer Armour & Clothing
Horse Mods
Overhauls - Main FCOM, WAC, TIE files.
Tamriel Travellers
Overhaul compatibility
Post Overhaul
Quests and Locations
Unique Landscapes
City overhauls
Overrides
Alternative starts
Vampires
Magic
Alchemy
Enchantment
Thievery, Sneaking and Crime
Guards and Bounty
Combat
Skills, Attributes and Leveling
Pose and Animation Mods
Semi-final overrides
Beauty Packs
Race Changes\Addons
Companions
Respawn & day length overrides
Shader mods
</pre>
<p class="empty"> </p>
<p>Since mod makers often take into account this evolving load order logic, an argument could be made that often even the replacers they use would account for this as well. There are many many exceptions to this ordering and so again the best place to refer to is the readme of each mod, BOSS, and general advice given in threads.</p>
<p class="empty"> </p>
<p>From my own installers list I've culled a similar install order which I present as my general recommendation for install ordering (Remember though every rule has an exception).</p>
<p class="empty"> </p>
<pre>
DCL
Unofficial Patches
DarN
Sounds
World textures - expandable
Environments
Weather
Other replacers
Overhauls - much
Overhaul Overrides and Patches
Quests
Dungeons
Locations
Houses
Unique Landscapes
Provinces/LOD
Cities and villages
Roads and infrastructure
Races and Bodies
Companions
Magic
Stealth
Combat
Scaling and leveling
errata
newly acquired and testing mods
my own projects
<code>====</code>
Unused Mods
</pre>
<p class="empty"> </p>
<p>These lists are not meant to be exhaustive and really are used for determining load order of plugins rather than to be considered for install orders.</p>
<p class="empty"> </p>
<p>I'm certainly not as familiar with Morrowind and what may be the best install order, but plan to research than and will revise this post when I do. The same goes for Fallout3.</p>
<p class="empty"> </p>
<p>The organization of installed packages can itself become a necessity as the list continues to grow. The following are suggestions for bringing order to the installed packages via naming and other methods.</p>
<p class="empty"> </p>
<h2 class="header2" id="NamingConventions">7.4.2 - Naming Conventions:</h2>
<p class="empty"> </p>
<p>Even with combining replacers and mods into complex packages and mashing as many errata files into other archives power mod users are likely to have an installer tab that is filled with many mods that can become confusing to navigate. This is where naming conventions can come in handy.</p>
<p class="empty"> </p>
<p>The common suffix for BAIN packages is simply the -BAIN at the end of the package. Although not necessary it does serve the purpose of letting one know that the package in question is supposed to be BAIN ready. Prefixes for packages have not been more fully thought out and this is an area where more tags could be used to notify the user of information.</p>
<p class="empty"> </p>
<p>When a package is put in the installer directory and after BAIN scans the package the package is assigned a number that relates to its install order. Because of this there is more freedom in naming the packages than there is with naming the sub-packages of a complex package. Prefixes can therefore be used to further tag a package with information that relates to common install orders or types of packages. Some examples might include:</p>
<p class="empty"> </p>
<pre>
REPLACER-World Textures-QTPIII-BAIN
REPLACER-Sky Textures Compilation-BAIN
OVERHAUL-Warcry-BAIN
OVERHAUL-MMM-BAIN
DUNGEONS-Dungeon Compilation-BAIN
DUNGEONS-David Brasher-BAIN
QUESTS-Simyaz-BAIN
QUESTS-Dragon Captions-BAIN
HOMES-Castles-BAIN
HOMES-Yevic Homes-BAIN
NEW LANDS-Tamriel Heightmaps-BAIN
NEW LANDS-Elsweyr-BAIN
SETTINGS-Leveling and Skills-BAIN
SETTINGS-Vanilla fixes-BAIN
</pre>
<p class="empty"> </p>
<p>These could also be abbreviated to one or two letters (I don't recommend numbers). And I'd think it not necessary to add them to every package as even a peppering of them would help the eye train in on what is essential. I've started using these tags with Fallout 3 and when peppered like that they are helping me see what is what faster. Spoiler of that installer list.</p>
<p class="empty"> </p>
<p>Another method is to create Markers to better organize the BAIN archive. They will show up as grey and look like the one that is automatically included named ==last== by doing this one could create dividers for the various packages along the lines of:</p>
<p class="empty"> </p>
<pre>
==Environment==
==Overhauls==
==Quests== ... and so on.
</pre>
<p class="empty"> </p>
<p>Using this as section headings you could create a very orderly looking BAIN archive that is easy to navigate and catalog. Sub-packages must be alpha-numeric in their naming in order to determine install order and override logic. Of course the conventions mentioned above do not have to be used. You could number every sub-package the same or different as long as the install order is as you want it and you know how to read it.</p>
<p class="empty"> </p>
<p>A few conventions have been promoted by myself and others:</p>
<p class="empty"> </p>
<p class="list-1">• If two sub-packages have competing data and only one should be installed then often they are named or numbered the same.</p>
<p class="list-1">• If mods are packed together and there are several main or core mods then the main mod often gets the numbering that starts a small series (i.e. 10) and each addition to it would complete that series (i.e. 11, 12 ... 16, 17, etc). With the next main mod starting the next series (i.e. 20).</p>
<p class="list-1">• The core of a mod that is essential is often packed at the lowest number (00 Core Mod).</p>
<p class="list-1">• Recently the idea of seperating docs into an extra core core package has been promoted (00 Core Mod docs).</p>
<p class="empty"> </p>
<p>The numbering does not have to stop at 99 either. you could number packages 110 ... 120, 125 ... 130, 131,132 ... 140 or as high and complicated as you like. Just remember then that lower number must contain as many digits as the higher numbers so 3 digits would need leading zeroes.</p>
<p class="empty"> </p>
<p>Alphanumeric ordering can be useful too. If all the mods in a package compilation are of the same type or named similarly and/or there is no need for install ordering (between sub-packages) then there is no harm in them having the same prefix designation. Such as the following:</p>
<p class="empty"> </p>
<pre>
Companion - Baddy
Companion - Eyja
Companion - Neeshka
or you could provide the mod authors name as a prefix if they have several of a type mods like
Umpa - Pose
Umpa - Martial Arts
</pre>
<p class="empty"> </p>
<p>Another method of bringing order to sub-packages is like the dummy archives above wherein one could create dummy sub-packages. One could make dummy esp (that should never be installed) or better yet rename a small texture into something that would never be accessed by a mod and place into an innocuous texture folder and it will install but not be used. (This is necessary as empty sub-packages will not appear as options in the sub-packages folder.) examples may include:</p>
<p class="empty"> </p>
<pre>
100 ==Animation mods==
110 Animation Mod A
120 Animation Mod B, etc
200 ==Idle mods==
210 Idles Mod A
220 Idles Mod B
300 ==Pose Mods==
310 Pose Mod A
320 Pose Mod B ... and so on.
</pre>
<p class="empty"> </p>
<p>Also using leading dashes '-' will work the same as the equal '=' sign.</p>
<p class="empty"> </p>
<h2 class="header2" id="Updatingbestpractices">7.4.3 - Updating best practices:</h2>
<p class="empty"> </p>
<p>The most important thing to remember is: Renaming packages means reinstalling it. Sad but true. Unfortunately if in updating a package you misname it or name it differently than what is currently installed then to BAIN it is a new package. You will have to install the package again which may mean reordering plugins and other annoyances.</p>
<p class="empty"> </p>
<p>One method of avoiding this mistake is possible - if you have the disc space for it - is to keep your mod catalog as a directory (preferably on another drive) with all the sub-packages prenamed, organized and ready to be zipped again at any time. What this, in essence, means is having two catalogs - one in the installers directory full of archives (packages) and the other in another directory unzipped yet containing both the downloaded original archives and the unzipped and organized archives. a lot, I know. Really it all about how much you want to get involved in this. External drives and other back up media could be very useful (but not burning one-off kind)</p>
<p class="empty"> </p>
<p>When using 7zip to create an archive you will find that by selecting folders to include as sub-packages to an archive that 7zip will automatically name the archive after whatever the directory is one level above the folders selected if they are all from the same directory (you of course can change the name). So if you name that upper/top directory after the name of the future package then that future package is automatically named for you.</p>
<p class="empty"> </p>
<p>Here is the protocol I use for updating:</p>
<p class="empty"> </p>
<p class="list-1">• Download your updated or original archive you want to include in an package compilation.</p>
<p class="list-1">• Extract the mod from a downloaded archive into a directory that is laid out like the future sub-packages under the directory named as the archive you want to create (or recreate).</p>
<p class="list-1">• Remove the downloaded archive and either store it or delete it.</p>
<p class="list-1">• Do the maintenance required (clean esp, redate esp, edit esp, optimize meshes, rename readme, etc).</p>
<p class="list-1">• Using 7zip select all the directories you want as sub-packages and click add (green plus sign).</p>
<p class="empty"> </p>
<p>create the archive and it will be named the same as the top directory.</p>
<p class="empty"> </p>
<p>What I do is also have another folder under each package directory called <code><B>_source</B>_</code> it contains the original archives (that I save). I've made enough mistakes in packaging that I've learned to save most things because I do not want to re-download repeatedly. the underscore is just a visual clue for me not to include it in the final product.</p>
<p class="empty"> </p>
<p>So here is the Et in Arkay-BAIN directory prior to archiving and installing:</p>
<p class="empty"> </p>
<pre>
Mod Catalog\Custom Bain Projects\quests\Et in Arkay Ego-BAIN
│
├[00 Et in Arkay Ego Core]
├[10 Spiritus Version]
├[20 Shivering Isles Patch]
├[25 Choices and Consequences Patch]
├[30 EiA Patch]
├[30 KotN Patch]
├[35 TOTF Patch]
├[50 UL Patch]
├[50 UL Patches Merged]
├___Source <- this folder contains the original archives - not included when zipping.
└ Et in Arkay Ego-BAIN.7z <- the final package to be placed in the installers folder.
</pre>
<p class="empty"> </p>
<p>Notice the directories above ending in the folder named like the archive created. I keep the extacted folders categorized and cataloged for convenience. Again I admit this is costly to disk space so use your discretion about what is best.</p>
<p class="empty"> </p>
<p>Another tip for speeding up both the compression process and speed up the scanning of new or updated packages is to use very light compression that is preferably non-solid. In the 7zip splash screen you will find Compression level (choose fastest) and further down Solid Block size (chose non-solid). This is again about a trade off as low compression means bigger packages and that means more disc space used. With less disc space you may need to choose high compression and that means a slower opening of the installers tab.</p>
<p class="empty"> </p>
<p>If you are updating a package that is named the same then prior to opening the installers tab remove the old package from the installers directory and replace with the new package (or overwrite). Then when the installers tab is opened it will scan and recognize the changes and give warning in the sub-tabs and in the colors of the packages. Simply make sure that all the options you want are chosen then right click on the package and click anneal. You may need to anneal other packages too and may further need to adjust load order of plugins or bash patch again or related activities.</p>
<p class="empty"> </p>
<p>If you are adding a package that has the same content as another package (such as BAIN ready mods being updated by the authors) and BAIN sees them as discreet and separate packages then it is best to move the newer package to prior to the older package in the install order, install the same options, then uninstall first and then delete the older and later install ordered package.</p>
<p class="empty"> </p>
<p>If you like the file trees I've been using and will continue to use in future posts and want to make them too the tool to use is called <a href="https://www.softpedia.com/dyn-postdownload.php/0a82bbbc275d9fc8f27916d638ba578a/5e12a5ff/1a4e5/4/1" >FileFolderTree</a> which will create these trees after choosing a directory to scan. Surazal created a Word 2007 Macro enabled document that will take the readouts generated and further reduce them to give only the sub-packages listed provided the sub-packages use numeric and not alphanumeric naming. This is available <a href="https://www.nexusmods.com/oblivion/mods/29790" >here</a> as a miscellaneous file.</p>
<p class="empty"> </p>
<p>Much thanks to Surazal for showing me this tool and creating the macro. A macro that you can import into Word 2007 is available <a href="http://forums.bethsoft.com/topic/957424-custom-bain-projects/?p=13906262" >in this post</a>. Surazal also provided many suggestions utilized in this selection. And one step further he created a Word Macro Enabled document to update the BOSS master list with your own updates called <a href="https://www.nexusmods.com/oblivion/mods/29790" >BOSS Master List Manager</a> (the main download).</p>
<p class="empty"> </p>
<h1 class="header1" id="CreatingYourOwnComplexBAINPackages">7.5 - Creating Your Own Complex BAIN Packages</h1>
<p class="empty"> </p>
<h2 class="header2" id="PlanningYourModArchive">7.5.1 - Planning Your Mod Archive</h2>
<p class="empty"> </p>
<p>After becoming familiar with BAIN packaging and repackaging you may want to give some consideration to how you will make BAIN ready the rest of your install and new mods that you come by.</p>
<p class="empty"> </p>
<p>Tomlong75210 provides a very persuasive argument that repackaging mods into complex packages is not ideal. As outlined above BAIN has the feature to open the download page of the mod if the package has the file extension that matches. That is great for checking for updates. Further there is the preference of sorting through simple packages in the installer tab rather than sub-packages through the sub-package filter. Doing this would render better conflict reports via the info-tabs. Tomlong's entire BAIN package (No updated Link) list illustrates how to organize such an enormous amount of packages.</p>
<p class="empty"> </p>
<p>To review the pros and cons I'd advise looking at what you want to accomplish. If you want to only use mods and delve into splitting replacers or doing cleaning and optimization of files and prefer easy access to Nexus and more comprehensive conflict reports then I'd advise Tomlong's method of keeping the packaging simple and originally named. If, on the other hand, you know how mods will conflict because you have reviewed that stuff to no end, you want to clean, optimize, break apart and/or combine salient mods together because you 'know' what you are doing then I'd recommend the very complex packages I will describe below.</p>
<p class="empty"> </p>
<p>Of course there is nothing preventing the use of both methods or the creation of your own. As I've learned more of Tomlong's method I would likely do it more that way if I were to reinstall all BAIN packages. That would take several weeks work to do and so not likely to happen. I see the advantages but believe that cleaning mods prior to packaging is the best option, even so in hindsight one could repackage as simple archives and append the file extension. Tomlong's package list comes out to 733 while mine comes out to 211 with each package containing further sub-packages. So whichever method you use (even both) is up to you.</p>
<p class="empty"> </p>
<h2 class="header2" id="RationaleforComplexCustomPackages">7.5.2 - Rationale for Complex Custom Packages</h2>
<p class="empty"> </p>
<p>Doubtless as one goes along in collecting and playing with mods there will come a point where they will want to combine mods in a variety of ways. This could be especially true when dealing with replacers like textures replacers and LOD. Often these two types of replacers can contribute greatly to performance lag and so many find that they have to test various different versions of a repalcer or remove aspects of a texture overhaul. Conversely others with a more powerful system may find that they can not only handle their favorite replacers but will want to add even more on top of those replacers. This will be trend as more powerful PC hardware is made available. This balancing act is part of creating a well modded Oblivion experience.</p>
<p class="empty"> </p>
<p>This section will deal with repackaging replacers into BAIN ready archives so that they are both broken down into component pieces and so that they could then be combined together with other replacers.There is no best practices for repackaging large, extravagant replacers but there are a few things to keep in mind. For one the conflict detection that BAIN offers between packages does not exist within packages and between sub-packages. So with this area of repackaging one will have to be much more conscious of what is being packaged and whether there are inherent conflicts. Doing this can take some time so that is something to consider.</p>
<p class="empty"> </p>
<p>The advantages to repackaging in this manner is really more about preference and control. Preference in that if you only liked certain aspects of a texture replacer, such as the clutter or architecture, and preferred the landscape and plant textures of another replacer set then breaking down the packages could be very worthwhile. Preference also in that this gives further ability to test performance and customize your install to fit the best performance models. Control in that if after building up what you think is a great combination and later find that maybe you need to tone down an aspect this provides a means of doing that be giving the option to remove certain portions.</p>
<p class="empty"> </p>
<p>There are a few different approaches to this. In my older thread I presented a model where I put Everything related to a texture overhaul in one giant archive This, however, has become very cumbersome and not an ideal approach. Primarily I wanted to see if I could do this and having done it the current size of that archive is 7 gigs. In fact so big that it is my intention to break this thing apart and start over. The internal structure though can provide a map for the individual packages.</p>
<p class="empty"> </p>
<p>When examining comprehensive texture replacers one may note that they cover many things from ground and road, to walls and ceilings ... from plants and trees to coins, cups, and furniture. These provide divisions in the texture replacer overhauls that we can use to create packages and sub-packages. When thinking about performance and due to the nature of the game it is easy to see that the game engine is not placed under as much stress when your character is in interiors as when outside and the game is rendering much more information. My own game has rarely ever crashed when my characters have been in interiors. this provides another reason and rationale for breaking apart texture replacer overhauls and packs.</p>
<p class="empty"> </p>
<p>So taking Qarls Texture Pack III into consideration here is a list of the main types of replacers it provides:</p>
<p class="empty"> </p>
<pre>
Architecture contains architecture folder, Qarl (Chorrol door?) and Wood (as it mostly was worked) textures.
Clutter contains only clutter textures.
Landscape contains landscape folder, Sky (only Snow), Plants (Butterflys?) textures
Rocks Contain only those meshes and textures
Dungeon Base contains Fort Ruins, Misc, Chargen (prisons) meshes and textures [I found no retextures of fort ruins?]
Ayleid Ruins contains only those meshes and textures
Caves Contain only those meshes and textures.
Sewers contain only those meshes and textures.
</pre>
<p class="empty"> </p>
<p>With these divisions it is easy to see that Architecture and Clutter can be found in interiors and exteriors. While Landscape and Rocks are most often used in exteriors and the rest are various replacers mainly seen in interiors (their interiors). This is not an exact division. Cave textures of course will include the entrances that are in the exterior world as do Sewers and especially Ayleid Ruins, and dungeons (forts). This may concern some but having a forest full of hi resolution trees will have a much greater impact upon performance than one hi resolution fort exterior. I'm certain that these exteriors could be further separated out if one wanted to research what is the exact pieces that are in the exterior. Thematically mixing and matching of textures could also be a factor and although you may squeeze minimal performance out of doing this it may not look great. Again that is a matter of preference.</p>
<p class="empty"> </p>
<p>With the above type of replacers we could then start to create packages in any number of combinations including:</p>
<p>1. Repackage a specific replacer but have the various types of textures further sub-divided as sub-packages.</p>
<p>2. Create solitary replacer packages of both a type and brand (i.e. QTPIII Architecture only).</p>
<p>3. Create combination packages of a type with several brands (i.e Architecture from 5 texture packs each sub-divided into sub-packages).</p>
<p class="empty"> </p>
<p>With thought-out naming and numbering conventions one could even do all three at once.</p>
<p class="empty"> </p>
<p>Taking Architecture as an example for choice 1 above one could create sub-packages for a texture replacer out of each folder within the Architecture folder.</p>
<p class="empty"> </p>
<input type="checkbox" id="spoiler1" />
<label for="spoiler1">Spoiler</label>
<div class="main-content">
<p>├[anvil]</p>
<p>│ └[anvilinterior]</p>
<p>├[arena]</p>
<p>├[basementsections]</p>
<p>├[bravil]</p>
<p>├[bruma]</p>
<p>│ ├[brumawallset]</p>
<p>│ └[interioronly]</p>
<p>├[castle]</p>
<p>│ ├[anvil]</p>
<p>│ └[cheydinhal]</p>
<p>├[castleinterior]</p>
<p>│ ├[narrowhalls]</p>
<p>│ └[towers]</p>
<p>├[cathedral]</p>
<p>├[cemetery]</p>
<p>├[cheydinhal]</p>
<p>│ └[interior]</p>
<p>├[chorrol]</p>
<p>│ └[interior]</p>
<p>├[daedricstatues]</p>
<p>├[doorstones]</p>
<p>├[farmhouse]</p>
<p>├[godstatues]</p>
<p>├[imperialcity]</p>
<p>│ ├[icbasementset]</p>
<p>│ └[icinterior]</p>
<p>├[leyawiin]</p>
<p>│ └[interior]</p>
<p>├[lowerclass]</p>
<p>│ └[lowinterior]</p>
<p>├[priory]</p>
<p>├[ships]</p>
<p>├[sidewalk]</p>
<p>├[skingrad]</p>
<p>├[statue]</p>
<p>│ ├[bravil]</p>
<p>│ └[kvatchstatue]</p>
<p>├[stonewall]</p>
<p>│ └[bravil]</p>
<p>└[tents]</p>
</div>
<p>This would be a very complex task especially if you were to then combine with other texture replacers so that only one option of each is installed. Option 1 above gives a lot of organization over a specific replacer set while Option 2 provides the most control with relation to other replacer sets. Option 3 probably has the main advantage of an economical replacer package in terms of managing your installers tab, but again using naming conventions could again make this redundant.</p>
<p class="empty"> </p>
<p>Of a cautionary note when having textures packs that may lay over the top (be lower in the install order) of other texture replaces it is important to note which versions may also have normal maps and or even meshes.</p>
<p class="empty"> </p>
<p>The main thing you want to avoid is having a texture replacer that also replaces meshes installing prior to a texture replacer that does not. The result could be that the meshes are looking for specific textures and those added by another replacer set may not be what is required even if named the same. The result could be graphic anomalies or performance issues. Of less of a concern is some textures have specific normal maps (texture add ons that give the appearance of a physical surface texture that provides more depth to the appearance of textures in game). More about understanding texture replacers at the Total Oblivion texture Overhaul (no optional link found except <a href="thishttps://www.yumpu.com/user/devnull.sweetdanger.net" ></a> and it didn't help much) site.</p>
<p class="empty"> </p>
<p>The advice is to make sure to package meshes and normal maps with the textures that they support and then to make those textures reside in either/or decision tree sub-packages so that other textures are not accidentally mixed in.</p>
<p class="empty"> </p>
<h2 class="header2" id="ExamplesofVeryComplexCustomBAINPackages">7.5.3 - Examples of Very Complex Custom BAIN Packages:</h2>
<p class="empty"> </p>
<p>These examples illustrate both the breaking apart of mods into component parts and the recombination of them with other mods that are also broken apart. The following examples of LOD and Sky Textures illustrate how one could mix and match component parts of mods with greater ease by having them repackages in this manner.</p>
<p class="empty"> </p>
<h2 class="header2" id="LODCompilation">7.5.4 - LOD Compilation</h2>
<p class="empty"> </p>
<p>This BAIN project combines most of the LOD variants available today. The package is divided up into five distinct sets of sub-packages or directories. The Core files are optional to use, Border regions are next, then the normal maps, color maps, and finally the optimized land meshes. Further the Shivering Isles maps are separated out for further customization. The purpose of this is to be able to have a BAIN archive that allows for easy switching between these mods in order to test mixing and matching, stability, and when what your looking at bores you. Most of these mods came as is and only cover the either normal or color maps. Zacherots, and Xerus had combined maps which I extracted and separated.</p>
<p class="empty"> </p>
<input type="checkbox" id="spoiler2" />
<label for="spoiler2">Spoiler</label>
<div class="main-content">
<p>LOD Compilation-BAIN</p>
<p>│</p>
<p>├[00 <a href="https://www.nexusmods.com/oblivion/mods/5127" >LOD NormalMap Fix MipMap Fix</a> ]</p>
<p>├[10 <a href="https://www.nexusmods.com/oblivion/mods/27023" >Border Regions Color -pk- 512</a> ]</p>
<p>├[10 <a href="https://www.nexusmods.com/oblivion/mods/5147" >Border Regions Color Blade -pk- 1024</a> ]</p>
<p>├[10 <a href="https://www.nexusmods.com/oblivion/mods/5147" >Border Regions Color Blade9722 2048</a> ]</p>
<p>├[10 <a href="https://www.nexusmods.com/oblivion/mods/2182" >Border Regions Color Shaja 2048</a> ]</p>
<p>├[20 <a href="https://www.nexusmods.com/oblivion/mods/27046" >Normal Maps -pk- 256</a> ]</p>
<p>├[20 Normal Maps -pk- 512]</p>
<p>├[20 <a href="https://www.nexusmods.com/oblivion/mods/18677" >Normal Maps CorePC Vibrant</a> ]</p>
<p>├[20 <a href="https://www.nexusmods.com/oblivion/mods/26911" >Normal Maps Deathb0rn 512</a> ]</p>
<p>├[20 Normal Maps Deathb0rn Vanilla]</p>
<p>├[20 <a href="https://www.nexusmods.com/oblivion/mods/11441" >Normal Maps Qarl 1024 Reduced</a> ]</p>
<p>├[20 Normal Maps Qarl 2048 Reduced]</p>
<p>├[20 <a href="https://www.nexusmods.com/oblivion/mods/18497/" >Normal Maps Qarl 4096 Compressed</a> ]</p>
<p>├[20 Normal Maps Qarl 512 Better Looking]</p>
<p>├[20 Normal Maps Qarl 512 Reduced]</p>
<p>├[20 <a href="https://www.nexusmods.com/oblivion/mods/17300" >Normal Maps Xerus 512</a> ]</p>
<p>├[21 <a href="https://www.nexusmods.com/oblivion/mods/17300" >SI Normal Maps Xerus 512</a> ]</p>
<p>├[25 <a href="https://www.nexusmods.com/oblivion/mods/27023" >Color Maps Main Landscape -pk- 1024</a> ]</p>
<p>├[25 Color Maps Main Landscape -pk- 2048]</p>