Several mods not loading due to same/similar error
I've been having a somewhat (seemingly) random issue for a while, pertaining to several mods being marked as being for the wrong version of tmodloader. However, as the actual indicated error seems to be the same for all of them, and appears mostly independent of what combination of mods I'm trying to enable, I believe there is/must be some underlying issue that's still there even if things suddenly work again for a while.
Notably, it pops up almost every time I use tmodloader after a period of not doing so / after it and several mods have been updated, though it often only happens after playing with the same mods once, with it failing to load on the next startup.
The particular (returning) error appears to be:
"System.ArgumentException: An item with the same key has already been added. Key: 92",
followed by (what I think is called) a traceback that varies somewhat depending on the enabled mods.
I've attached a screenshot of one example error I get within tmodloader itself. Searching through my client log shows that the same error/exception is also being caught regularly without causing an error, though this is often right before the same issue causes a mod to fail to load.
One last note is that I think there's a throughline in what mods have this issue, in that it only seems to happen with mods that add music. For example, while Calamity has not triggered this particular error, its linked music mod has done so repeatedly.
Notably, it pops up almost every time I use tmodloader after a period of not doing so / after it and several mods have been updated, though it often only happens after playing with the same mods once, with it failing to load on the next startup.
The particular (returning) error appears to be:
"System.ArgumentException: An item with the same key has already been added. Key: 92",
followed by (what I think is called) a traceback that varies somewhat depending on the enabled mods.
I've attached a screenshot of one example error I get within tmodloader itself. Searching through my client log shows that the same error/exception is also being caught regularly without causing an error, though this is often right before the same issue causes a mod to fail to load.
One last note is that I think there's a throughline in what mods have this issue, in that it only seems to happen with mods that add music. For example, while Calamity has not triggered this particular error, its linked music mod has done so repeatedly.
