Now you can slowly add in the mods from the last removed batch, and single out which mod in that group is causing a conflict. As soon as the errors do not exist, you can assume the last batch of removed mods includes at least one of the conflicting mods. You continue this process until the errors do not exist. If the errors are still there, you remove another half of your loaded mods and restart the game (do not add the previously removed mods back into the active mods). Then you restart RimWorld and see if the same errors/behavior persist. It will be the most practical method for most users.Ī binary search requires that you de-activate half of your loaded mods from the active mod list. This is the most simple method, but also more time consuming that deciphering an error log. Once you identify errors you can start a binary search to single out the mods with conflicts. mod missing functionality that is added by other mods (items, hair, animations, etc.mod missing functionality after other mods enabled (gizmos, actions, etc).exceptions/errors (red text in console).It should be noted that in all testing it is assumed you always load required depedencies for any mods. As always you should read mod descriptions/documentation and only report errors that are unmentioned. Adding/removing mods mid-game should not be done unless you know what you are doing and accept that responsibility.
Adding or removing mods in an ongoing game will likely give false-positives and is poor practice. It may also appear as a bug in a new save game, with unexpected/odd behavior occuring. An error usually appears as red text in the debug log once RimWorld boots. To start the testing method you must first identify an error. Create rules only for mods that interact with each other in the way that causes issues, you know exact mods that causes the issue (you have followed instruction below to do that) and you can replicate the issue, never create rule just because you think "that is a good mod order position".
0 kommentar(er)
