Messages

read about version compatability mod folder structure.

your textures must be placed into "common" folder and referenced properly from data and code.

alternative check is "canbleed" and treat all pawns that can't bleed as mechanical, helps with mod compatability.

use notepad++ or any other similar tool to search given string inside mods and steam workkshop mods folders

as long as mod author not implemented that string as hardcoded and not obfuscated his DLL, you will instantly get answer to your question.

https://github.com/Mehni/ExampleJob/wiki

static reference to managed object is not "function" and it works by giving you reference to managed object

with devmode off log popup is something is wrong only

start without mods
enable mods in small batches

start with something extra simple, like xpatch specific field of vanilla object
then do exactly same operation if specific mod is present

after understanding concept (and making sure that mod name and other data is okay) do what you originally planned.

also you may inject additional trace\debug output into classes like Verse.PatchOperationFindMod to make extra sure, that everything works as you intended.

mod loading order?
other errors earlier?

you should not promote your personal preferences for no reason.

it's okay to say something like:
Software X lack feature Y but software Z have all features.

But absolutely not okay to say:
Software X is old do not use it because i don't like it.

\what exactly issue you have with monodevelop, probably some error, lack of feature, or anything similar?

lack of updates is not issue on it's own, you can run software not updated in DECADES just fine (and your PC won't turn into pumpkin if you run windowsXP)

https://www.monodevelop.com/

eh?

enable mods in __small__ batches

installing 350 mods at once and expecting everything to work perfectly is very strange move.

1) Exact version does not matter, only token and version does.
Game have version 400 with token "b77a5c561934e089" and this is exactly same token, that listed in original error message.
You do not need exactly same version of mscorlib, you need one with same token and version.

2) Game do load files one by one in alphabetical order, this is exactly reason, why libs normally called "000_name" and similar to ensure them loading before assemblies, that have references to said libraries.

3) Rename your json library into something like 000000JSON.dll, this will make game load your library first and references to library won't be invalid.

4) b03f5f7f11d50a3a is different token, ever if version of mscorlib exactly same, due to different token, it won't be recognized.

5) There are workarounds to force runtime to accept references ignoring version and token, read about side effects before using them.

kay, i will ask you question, what version of mscorlib your version of game have?