Difference between revisions of "TES5Edit Documentation"

To begin, Right-click in the Left-Side Panel and select, “Apply Filter” as shown in Step 1 and 2 below:

To begin, Right-click in the Left-Side Panel and select, “Apply Filter” as shown in Step 1 and 2 below:

The Filter window will now be presented, allowing you to check and un-check options according to the screenshot below (which are the settings for conflict detection).

The Filter window will now be presented, allowing you to check and un-check options according to the screenshot below (which are the settings for conflict detection).

In the example screenshot below of the Filter window, the options A-E are the Only options that should be checked, after which you can click, “Apply” (F) to start the filter.

In the example screenshot below of the Filter window, the options A-E are the Only options that should be checked, after which you can click, “Apply” (F) to start the filter.

Once you click on Filter (F), XEdit will filter and analyze all of the loaded mods against the conflict-detection algorithm. This may take some time depending on how many mods you have loaded and how robust your computer is. The progress is shown in the upper-right corner of XEdit as the screenshot below illustrates:

Once you click on Filter (F), XEdit will filter and analyze all of the loaded mods against the conflict-detection algorithm. This may take some time depending on how many mods you have loaded and how robust your computer is. The progress is shown in the upper-right corner of XEdit as the screenshot below illustrates:

XEdit also keeps track of how long the filter takes to apply. If you run 100+ mods, it can take several minutes to process all of the data. Conflict detection is not simply based on the existence of multiple records for the same FormID in different modules but instead performs a comparison of the parsed sub-record data via an algorithm.

XEdit also keeps track of how long the filter takes to apply. If you run 100+ mods, it can take several minutes to process all of the data. Conflict detection is not simply based on the existence of multiple records for the same FormID in different modules but instead performs a comparison of the parsed sub-record data via an algorithm.

The screenshot below illustrates how XEdit will look once the conflict detection process is complete. Note the [Filtering done] block in the Messages Tab below (A), indicating both the success of the conflict filtering process as well as record and time statistics about the filtration result. The screenshot below shows a typical outcome:

The screenshot below illustrates how XEdit will look once the conflict detection process is complete. Note the [Filtering done] block in the Messages Tab below (A), indicating both the success of the conflict filtering process as well as record and time statistics about the filtration result. The screenshot below shows a typical outcome:

The mods-list in the Left-Side Panel changes as the filter adjusts the text color and background color based on conflict status. The View Tab will show the actual conflicts, but only when you select on a record in the Left-Side Panel as shown below:

The mods-list in the Left-Side Panel changes as the filter adjusts the text color and background color based on conflict status. The View Tab will show the actual conflicts, but only when you select on a record in the Left-Side Panel as shown below:

With that you now understand how to detect for conflicts with XEdit and where to look at the data. You‟re now ready to learn about colors and display order. Understanding the color schemes behind the text and backgrounds is critical to understanding the conflicts, and how to resolve them.

With that you now understand how to detect for conflicts with XEdit and where to look at the data. You‟re now ready to learn about colors and display order. Understanding the color schemes behind the text and backgrounds is critical to understanding the conflicts, and how to resolve them.