RuntimeOCD

As the game loads XML files from mods, RuntimeOCD obsessively analyzes them to detect potential conflicts between them. Once a conflict is detected, it is logged for troubleshooting or debugging purposes. Only the host can see these log entries. Logs, along with configuration files, are written to Roaming/7DaysToDie/RuntimeOCD.

In additon to this, RuntimeOCD patches specific well-defined conflicts on the fly to improve compatibility and/or to prevent the game from displaying specific errors to players when they do not pose any real problems (more info below).

Glossary of pertinent XML lingo

• []

  Element

  : an element as defined in XML.[/]

  []

  Type

  : an element's XML node name (like block, buff, item, property, enemy, etc). They are called "names" in XML but I'm calling them "types" here to avoid confusion with the "name" attribute.[/]

  []

  Descendant

  : an element that is a under another element in the XML tree, i.e. the child of another element, or the child of a child, etc. An Ancestor would be the inverse.[/]

  []

  Sibling

  : an element that has the same parent element as another element.[/]

  This whole thing is an element:

  <type attribute="value">

  </type>

  These are four elements:

  <Rick_Sanchez>

  <Beth_Sanchez>

  <Summer_Smith/>

  <Morty_Smith/>