Skip to main content
Tweeted twitter.com/TheArqade/status/764355432370540544
deleted 56 characters in body
Source Link
nedsociety
  • 63
  • 1
  • 1
  • 4

In Skyrim, there are lots of mods that influence other mods' functionality. To handle those side effects, lots of them are providing compatibility patches for other common mods.

Now let's get to the modder's perspective. If I target a perfectly pre-arranged mod list (such as STEP) and install them one-by-one from the beginning, it is possible to grab all of those patches by carefully navigating each of mod pages.

Unfortunately, when editing an existing mod list, it doesn't work because most patches are provided from only one of the mod pages. When installing an additional mod X, it is quite easy to overlook a patch between X and any of existing mods, unless it is provided on X's mod page. Similar thing happens when removing a mod. This becomes even worse when realizing that some of the patches are provided only within FOMOD installers, not even mentioned on the mod pages at all.

Is there a way to manage this task? Definitely the Mod Manager doesn't help that much here. Should I really build a database of mod pairs for every possible patches?

In Skyrim, there are lots of mods that influence other mods' functionality. To handle those side effects, lots of them are providing compatibility patches for other common mods.

Now let's get to the modder's perspective. If I target a perfectly pre-arranged mod list (such as STEP) and install them one-by-one from the beginning, it is possible to grab all of those patches by carefully navigating each of mod pages.

Unfortunately, when editing an existing mod list, it doesn't work because most patches are provided from only one of the mod pages. When installing an additional mod X, it is quite easy to overlook a patch between X and any of existing mods, unless it is provided on X's mod page. Similar thing happens when removing a mod. This becomes even worse when realizing that some of the patches are provided only within FOMOD installers, not even mentioned on the mod pages at all.

Is there a way to manage this task? Definitely the Mod Manager doesn't help that much here. Should I really build a database of mod pairs for every possible patches?

In Skyrim, there are lots of mods that influence other mods' functionality. To handle those side effects, lots of them are providing compatibility patches for other common mods.

Now let's get to the modder's perspective. If I target a perfectly pre-arranged mod list (such as STEP) and install them one-by-one from the beginning, it is possible to grab all of those patches by carefully navigating each of mod pages.

Unfortunately, when editing an existing mod list, it doesn't work because most patches are provided from only one of the mod pages. When installing an additional mod X, it is quite easy to overlook a patch between X and any of existing mods, unless it is provided on X's mod page. Similar thing happens when removing a mod. This becomes even worse when realizing that some of the patches are provided only within FOMOD installers, not even mentioned on the mod pages at all.

Is there a way to manage this task? Should I really build a database of mod pairs for every possible patches?

edited title
Source Link
nedsociety
  • 63
  • 1
  • 1
  • 4

How do you manage the dependencycompatibility between mods in Skyrim?

In Skyrim, there are lots of mods that influence other mods' functionality. To handle those side effects, lots of them are providing compatibility patches for other common mods.

Now let's get to the modder's perspective. If I knowtarget a perfectly arrangedpre-arranged mod list (such as STEP) and install them one-by-one from the beginning, it is possible to grab all of those patches by carefully navigating each of mod pages.

Unfortunately, when editing an existing mod list, it doesn't work because most patches are provided from only one of the mod pages. When installing an additional mod X, it is quite easy to overlook a patch between X and any of existing mods, unless it is provided on X's mod page. Similar thing happens when removing a mod. This becomes even worse when realizing that some of the patches are provided only within FOMOD installers, not even mentioned on the mod pages at all.

Is there a way to manage this task? Definitely the Mod Manager doesn't help that much here. Should I really build a database of mod pairs for every possible patches?

How do you manage the dependency between mods in Skyrim?

In Skyrim, there are lots of mods that influence other mods' functionality. To handle those side effects, lots of them are providing compatibility patches for other common mods.

Now let's get to the modder's perspective. If I know a perfectly arranged mod list and install them one-by-one from the beginning, it is possible to grab all of those patches by carefully navigating each mod pages.

Unfortunately, when editing an existing mod list, it doesn't work because most patches are provided from only one of the mod pages. When installing an additional mod X, it is quite easy to overlook a patch between X and any of existing mods, unless it is provided on X's mod page. Similar thing happens when removing a mod. This becomes even worse when realizing that some of the patches are provided only within FOMOD installers, not even mentioned on the mod pages at all.

Is there a way to manage this task? Definitely the Mod Manager doesn't help that much here. Should I really build a database of mod pairs for every possible patches?

How do you manage the compatibility between mods in Skyrim?

In Skyrim, there are lots of mods that influence other mods' functionality. To handle those side effects, lots of them are providing compatibility patches for other common mods.

Now let's get to the modder's perspective. If I target a perfectly pre-arranged mod list (such as STEP) and install them one-by-one from the beginning, it is possible to grab all of those patches by carefully navigating each of mod pages.

Unfortunately, when editing an existing mod list, it doesn't work because most patches are provided from only one of the mod pages. When installing an additional mod X, it is quite easy to overlook a patch between X and any of existing mods, unless it is provided on X's mod page. Similar thing happens when removing a mod. This becomes even worse when realizing that some of the patches are provided only within FOMOD installers, not even mentioned on the mod pages at all.

Is there a way to manage this task? Definitely the Mod Manager doesn't help that much here. Should I really build a database of mod pairs for every possible patches?

Source Link
nedsociety
  • 63
  • 1
  • 1
  • 4

How do you manage the dependency between mods in Skyrim?

In Skyrim, there are lots of mods that influence other mods' functionality. To handle those side effects, lots of them are providing compatibility patches for other common mods.

Now let's get to the modder's perspective. If I know a perfectly arranged mod list and install them one-by-one from the beginning, it is possible to grab all of those patches by carefully navigating each mod pages.

Unfortunately, when editing an existing mod list, it doesn't work because most patches are provided from only one of the mod pages. When installing an additional mod X, it is quite easy to overlook a patch between X and any of existing mods, unless it is provided on X's mod page. Similar thing happens when removing a mod. This becomes even worse when realizing that some of the patches are provided only within FOMOD installers, not even mentioned on the mod pages at all.

Is there a way to manage this task? Definitely the Mod Manager doesn't help that much here. Should I really build a database of mod pairs for every possible patches?