The following reasoning can be read quite often: "I had Mod X, Mod Y, Mod Z installed and everything was fine, but when I installed Mod K, I experienced the bug you are talking about. Uninstalling Mod K helped, so it was the culprit I think.". The answer of the other person: "I uninstalled Mod K but the bug did not disappear for me... interesting."
I would like to point out that simple logical reasoning doesn't always give a correct result (but, of course, it can be a good basis for further investigation). Let me tell an example. (You can find a graphical illustration attached to this post; feel free to use it while reading my below lines).
There is Mod A, Mod B, Mod C and Mod D. The player wants to enjoy Mod A at any cost, but if possible, he would like to use Mod B, Mod C and Mod D as well. Mod B introduces a bug (for example, corrupts a file), but the bug doesn't appear in-game when only Mod A and Mod B are installed, because it doesn't affect Mod A. In fact, the bug doesn't appear in-game even when Mod C is installed, because the bug doesn't affect Mod C either. So we have three mods, Mod A, Mod B and Mod C installed, in this order, and Mod B is buggy, but the player doesn't experience anything! On the other hand, the bug introduced by Mod B affects Mod D (e.g. because Mod D uses the corrupted resource). So when Mod D is installed and the player starts to play, the bug appears. For example, his or her game crashes! "Oh no, Mod D corrupted the game! It's buggy!"
So bugs can be tricky! They might not appear in the game immediately or cause any problems, but in certain circumstances (e.g. mod combinations), they are "activated"! Like certain types of computer viruses, which trigger at a given time or in certain conditions.
A few consequences:
- Just because you believe a mod caused a bug, don't condemn it immediately or remove it from your list forever (unless it's evident that the mod caused the bug)! Report it instead, and consider the opinion of skilled mod developers and testers. Of course, if you cannot solve the problem and/or want to play without the bug, you can uninstall it but don't forget that it might be the mod combination and not the mod which was responsible for the bug. That is, it's possible that another mod is buggy, but a harmless mod triggered the bug in the game!
- As I emphasized countless times in the past, the statement "it's not a bug as long as it doesn't appear in-game" is nonsense. Unless you can prove that the bug will never appear in-game in any (reasonable) circumstances, the bug remains a threat and should be fixed.
- For the above reasons, not all bugs can be recognized during tests. It would be required to test a mod with all other possible mods (or at least, with all other typical mod types that might interact with the tested mod), and this is impossible. This is why it's so tremendously important to correctly design and build a mod, and not to exclusively rely on testing!
- The more complex a mod is, the more sensitive it is to the bugs, errors, negligences of other mods. For example, this is why Improved Anvil has so precise installation instructions. Latent, hidden bugs might do absolutely nothing with smaller projects, but a huge mod that relies on many resources and elements of the game (such as Improved Anvil) can easily be broken even by the smallest (but subtle) bug or flaw of a smaller mod!
- In the past, I was the subject of the criticism of certain mod makers who demanded "practical examples" from me to prove my (theoretically and logically estabilished, proved) statements about certain things. As you can see, practice isn't everything. Sometimes skills and experience can help much more than practical tests when recognizing potential errors, problems.
It is important to note that this is a short summary that focuses on a very specific topic. For example, I could have written about bug types as well. There are bugs which don't have any spectacular consequence in the game. In fact, the effect of certain bugs is unnoticeable. BWL's Distinguished Developer, Sikret also pointed it out that these bugs can be really subtle and players usually don't notice them at all. E.g., a bug in a certain mod might prevent another (big) mod's quest from triggering. That is, the player even doesn't realize that the quest exists. No bug is reported! Yet, when it happens with more quests (they simply don't trigger or they behave in an undesired way) the author of the big mod won't be too happy; while the creator of the buggy mod can simply answer "there were no bug reports, where is the bug?". The author of the big mod shows the bug, it gets fixed. But when a mod is poorly designed and tested, it will be a continus source of bugs, and if its developer doesn't (want to) realize this (and doesn't want to revise the whole mod) and demands "concrete examples" of bugs instead, the problem just becomes bigger... It surprises me when certain mod makers ignore or reject the advice and criticism they get, because they are too self-confident and believe they can't be wrong and their methods/techniques are seamless. Instead of considering the advice and possibly improving their skills!
So it does matter very much how precisely/thoroughly mod authors design and test their works. Some authors say that too much attention spoils the fun of development, but I'm sure there is a level where fun and hard work is balanced (let alone the future advantages of a well-made mod).
