forked from Sharlikran/xEdit
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Memo1.txt
215 lines (158 loc) · 10.7 KB
/
Memo1.txt
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
xEdit is an advanced graphical esp editor and conflict detector.
Discord: https://discord.gg/5t8RnNQ
Forum: https://afkmods.iguanadons.net/index.php?/topic/3750-wipz-tes5edit/
The navigation treeview on the left side shows all active masters and plugins in their correct load order. By navigating that treeview you can look at every single record in any of your masters or plugins. Once a record has been selected the detailed contents of that record is shown on the right side.
The view treeview shows all versions of the selected record from all plugins which contain it. The left most column is the master. The right most column is the plugin that "wins". This is the version of the record that the game sees.
The navigation and view treeview use the same color coding to signal the conflict state of individual fields (in the view treeview) and the record overall (in the navigation treeview).
Previously colors were listed by background and text color. Instead, click the Legend button in the upper right corner. The Legend window will summarizes the meaning of the colors.
Conflict detection is not simply based on the existence of multiple records for the same FormID in different plugins but instead performs a comparison of the parsed subrecord data.
The navigation treeview has a context menu where you can activate filtering. Filtering is based on the same conflict categorization as the background and text color.
Command Line Switches:
-cp:<codepage> or -cp-trans:<codepage> [sets codepage for translatable strings to codepage number or utf8]
-l:<language> [Sets language, affects used codepage and .strings files]
-edit [Enable Edit Mode]
-view [Enable View Mode]
-saves [Enable Saves Mode / View Mode Only]
-IgnoreESL [Will load all modules as full modules, even if ESL flagged]
-PseudoESL [xEdit will check if the module falls within ESL constraints (not containing new records with ObjectIDs > $FFF) and load the file like an ESL (mapped into the FE xxx namespace) if possible]
-DontCache [Completely disables ref caching]
-DontCacheLoad [Don't load cache files if present, but save if possible]
-DontCacheSave [Don't save cache files after building refs]
-AllowDirectSaves:<filename list> [File may be an .esm, .esl, or .esp. Without a list of files, this will load non-official (official = game master, official dlcs, CCs) modules without using memory mapped files. Optionally you can specify a list of files. Which will only load the listed modules without using memory mapped files. This optional list may include official modules.]
-<gamemode> [Specifies which game mode to use. <gamemode> can be any of the following: 'tes5vr', 'fo4vr', 'tes4', 'tes5', 'enderal', 'sse', 'fo3', 'fnv', 'fo4', 'fo76']
-moprofile:<profilename> Opens the plugin selection from the MO profile named in the switch.
-setesm [Set ESM flag. Plugin selection screen will appear.]
-clearesm [Remove ESM flag. Plugin selection screen will appear.]
-VeryQuickShowConflicts [loads all modules according to plugins.txt without showing module selection, except if CTRL is pressed on start]
-quickclean [cleans and prompts to save the file]
-quickautoclean [Cleans 3 times and saves in between each step]
-C:<path> [path to use for cache files]
-S:<path> [Path to look for scripts]
-T:<path> [Temporary Directory]
-D:<path> [Specify a Data Directory]
-O:<path> [Specify path for generated LOD files]
-I:<path> [Game INI Files]
-G:<path> [Save Game Path]
-P:<path><filename> [Custom Plugins.txt file]
-B:<path> [Backups path i.e. Edit Backups\]
-R:<path><filename> [Custom xEdit Log Filename]
All path parameters must be specified with trailing backslash.
Keyboard Shortcuts:
- Holding Shift+Ctrl+Alt while starting shows a dialog asking if the setting file should be deleted.
- Holding Shift while starting to reset window position
Module Selection Treeview:
- Hold SHIFT to skip building/loading references for all plugins.
- [UP/DOWN] arrow to navigate plugin list. If multiple plugins are selected, this will deselect them.
- [Space] to check or uncheck selected plugins.
Main Treeview:
- Ctrl + S Create temporary save.
- Ctrl + F3 to open Assets Browser
- Alt + F3 to open Worldspace Browser
Navagation treeview:
- Ctrl + 1 through 5 to set a Bookmark.
- ALT + 1 through 5 to jump to a Bookmark.
- F2 to change FormID of a record
- Ctrl or Shift while clicking to select several records/plugins at once
- Del To delete a record or a group of records
- Alt + Click to fully expand a tree. This can take a lot of time when expanding large trees.
- [Right Arrow] or + to expand current node
- [Left Arrow] or - to collapse current node
- * Expand treview (recursive)
- / Collapse treeview (recursive)
View treeview:
- Ctrl + UP/DOWN to move elements in unordered lists.
- F2 to activate inplace editor
- CTRL + Click on FormID to switch focus to that record
- [Double Click] on text field to open multiline viewer
- [Double Click] on [Integer, Float, or FormID] to open In-Place Editor
- Shift + [Double Click] on text field to open multiline editor
- Ctrl + C to copy to clipboard
- Ctrl + W from a weather record to open the visual weather editor
- Alt + CRSR while in view treeview to navigate within the Navagation treeview
Messages tab:
- CTRL + [Double Click] on FormID to switch focus to that record
Modgroup Editor:
- CTRL UP/DOWN - Move entry
- INSERT - Insert entry (Insert Module or CRC depending on which is selected)
- SHIFT + INSERT - Insert crc (when on a module)
- DELETE - Delete a module or crc
- SPACE / Mouse Click - toggle flag when a flag is currently focused
Modgroups:
For a modgroup the be activateable, the order of the mods in the load order and modgroup must match.
If a modgroup is active, what it essentially means is that for each record that is contained in more than one mod of the modgroup, only the last (in load order) is visible. That's it. The invisible record versions simply don't participate in the normal conflict detection mechanisms at all.
A modgroup does not perform any merge or make any changes to any mod. All it does it hide away version of records that you've stated (by defining the modgroup) that you've already checked them against each other and the hidden record is simply irrelevant.
Modgroups File and Syntax:
[xEdit EXE Name].modgroups i.e. SSEEdit.modgroups for SSEEdit. Save in the same folder as the EXE.
[Plugin Name].modgroups i.e. for Someplugin.esp, Someplugin.modgroups. Save the file in your Data folder instead.
Prefixes are processed from left to right. #@Plugin.esp is the same -Plugin.esp. They combine "negatively" not positively.
without prefix file is both a target and a source
+ The file is optional
- The file is neither a target nor a source.
} Ignore load order completely
{ Ignore load order among a consecutive block of mods marked with this.
@ File is not a source
# File is not a target
! File is forbidden. If the listed module is active, the modgroup is invalid.
<filename>:CRC32
If a module is followed by a list of one or more CRC values, the modgroup is only available if the module has one of the listed CRCs. Source means that if a record in this mod is found, then it will hide the versions of the same record from all mods listed above it that are targets.
[Modgroup Name]
MainPlugin.esm
MainPlugin - A.esp
MainPlugin - B.esp
MainPlugin - C.esp
MainPlugin - D.esp
MainPlugin - E.esp
The above example means that all in that particular order for the modgroup to be activateable.
[Modgroup Name A]
-MainPlugin - C.esp
MainPlugin - D.esp
MainPlugin - E.esp
[Modgroup Name B]
MainPlugin - C.esp
-MainPlugin - D.esp
MainPlugin - E.esp
Group A) If a record is present in E and D, the records from plugin D will be hidden.
Group B) If a record is present in E and C, the records from plugin C will be hidden.
[Modgroup Name]
MainPlugin - C.esp:12345678
MainPlugin - D.esp:A1B2C3D4,F9E8D7C6
MainPlugin - E.esp
Not all mod groups defined in that file will necessarily show up in the selection list. Mod groups for which less then 2 plugins are currently active are filtered. If the load order of plugins doesn't match the order in the mod group it is also filtered.
What's the effect of having a mod group active?
When a record for the view treeview is generated and multiple files of the same mod group modify this record, then only the newest of the files in that modgroup will be shown. So instead of seeing 5 different files with numerous conflicts you are only seeing the newest file in that mod group. This also affects conflict classification.
It's worth pointing out here that if a record is overridden by both plugins in a mod group and other plugins that normal conflict detection will still work perfectly.
Basically this system can be used to reduce a lot of noise from the conflict reports.
Reference Caching:
[GameMode]\Data\FO4Edit Cache
Cache files are based on the CRC of the xEdit EXE, then the plugin filename. For example 3917E178_DLCNukaWorld_esm_43D25C56.refcache. Once built xEdit will load the cache file rather then build the references again. This reduces load time.
xEdit Backup Files:
[GameMode]\Data\FO4Edit Backups
Backups are saved with the file name [PluginName].[esm/esp/els].backup.[Date Stamp} For example PluginName.esp.backup.2018_07_25_20_52_10. These can be renamed and copied to the Data folder.
Show Only Master and Leafs:
What this does is, similar to modgroups, reduce which records are being show in the view treeview (and are taken into account for calculating conflict information).
Suppose you have the following mods:
+------------+
| |
| Master |
| |
+----^-------+
|
| +--------------+ +-------------+
| | <----------------+ |
+-------+ A | | D |
| | <-----+ | |
| +--------------+ | +-------------+
| |
| +--------------+ | +-------------+
| | | +----------+ |
+-------+ B | | E |
| | <----------------+ |
| +--------------+ +-------------+
|
| +--------------+
| | |
+-------+ C |
| |
+--------------+
Then with active "Only Master and Leafs" only Master, D, E, and C will be shown. The assumption here being that whatever the contents of A or B, it's already being taken into account by D and/or E.
This assumption is obviously only true if the author of mods D and E did their job correctly, so this isn't a good option to have always enabled. As long as that assumption holds true, it can declutter the reported conflicts significantly.