Difference between revisions of "TES5Edit Documentation"

Understanding the color schema is a key to understanding XEdit. The color coding schema is designed to make the process as simple and efficient as possible. The legend below will introduce you to the basic color schema:

Understanding the color schema is a key to understanding XEdit. The color coding schema is designed to make the process as simple and efficient as possible. The legend below will introduce you to the basic color schema:

The same color schema is used for the Left-Side Panel as well as in the Right-Hand View Tab, which shows the actual conflicts. This is done for consistency, with the text/background color of the left-hand mod-list determined by the conflicts in the right-hand window. There are many cases in which the status shows a conflict has occurred (red background), but that no action needs to be taken.

The same color schema is used for the Left-Side Panel as well as in the Right-Hand View Tab, which shows the actual conflicts. This is done for consistency, with the text/background color of the left-hand mod-list determined by the conflicts in the right-hand window. There are many cases in which the status shows a conflict has occurred (red background), but that no action needs to be taken.

The sample below shows both the color schema and the display-order together to better illustrate how conflict detection works. XEdit displays each conflict in the order that the files are loaded (FOMM‟s load order), with the first mod loaded listed on the Left (Purple) and the last mod loaded listed on the Right (Orange).

The sample below shows both the color schema and the display-order together to better illustrate how conflict detection works. XEdit displays each conflict in the order that the files are loaded (FOMM‟s load order), with the first mod loaded listed on the Left (Purple) and the last mod loaded listed on the Right (Orange).

All conflicts are ordered this way, with any mods loaded in-between either in a conflict state (Red) or that is identical to the Master (Grey) as described above.

All conflicts are ordered this way, with any mods loaded in-between either in a conflict state (Red) or that is identical to the Master (Grey) as described above.

The Load Order Workflow chart below is designed to help you understand the different color-combinations that you will encounter when de-conflicting mods. The XEdit display order as shown above was transposed into the vertical diagram below to help better illustrate how XEdit determines conflict winners and losers:

The Load Order Workflow chart below is designed to help you understand the different color-combinations that you will encounter when de-conflicting mods. The XEdit display order as shown above was transposed into the vertical diagram below to help better illustrate how XEdit determines conflict winners and losers:

As the chart above illustrates, the last-file loaded is always the conflict winner and ultimately determines what loads into Fallout: New Vegas. In this example NV-Phalanx got lucky that MyPatchPlugin mod shared the same Flagging, or they would have been conflict losers to the Flagging set by Cuter Veronica. However the Cuter Veronica mod is the conflict looser, and in this case we want Cuter Veronica to be the winner in terms of Hair and other body data.

As the chart above illustrates, the last-file loaded is always the conflict winner and ultimately determines what loads into Fallout: New Vegas. In this example NV-Phalanx got lucky that MyPatchPlugin mod shared the same Flagging, or they would have been conflict losers to the Flagging set by Cuter Veronica. However the Cuter Veronica mod is the conflict looser, and in this case we want Cuter Veronica to be the winner in terms of Hair and other body data.