dnSpy VS JustDecompile Engine

Protip: Use a debugger like dnSpy or Visual studio to trace the source of error, by stepping the program line by line. You can restart with dnSpy attached.

Download dnSpy, Open the file "assembly_valheim.dll", Select view and then Assembly Explorer, search for DLCMan class (if you have trouble there is a search tool in the top bar, doing so you'll find the whole class), went to the correct lines (50, 79, 97 even if for me it was actually 98), right click on edit method/class (might be better to use method) and change the " return false; " to " return true; ". After the process compile again and there you have it.

To inspect the code, I recommend dnSpy. https://github.com/dnSpy/dnSpy You want to run it on the Assembly-CSharp.dll file from _Data/Managed. Then you can view the source code. I searched the entire project for the word "pause" until I found something that looked relevant. Luckily, the code for this game is pretty well written and well laid out.

It's dnSpy.

Great question! The tool I used, DNSpy, has the ability to patch in opcodes. So I just put in the instructions needed as essentially assembly, and I did so by just writing bytes into the existing executable. The two I used were ldc.i4 to put an integer onto the stack, and then mul to multiply it with the existing value.

.NET is super easy to reverse, you don't need Ghidra, go try dnSpy, that should do the trick.

Code Creation. Unfortunately, I don't have more information on the code of the game. This is the part I need help with. I'm quite familiar with HTML, CSS, and Javascript, but haven't really touched C#. The best that I've managed is opening Kitchen.Common.dll and KitchenMode.dll in dnSpy (https://github.com/dnSpy/dnSpy) and looking at the class and struct names, recognizing that some of the contents of those dll files which start with C, like CAppliance, are components of entities in the game, and can be used to retrieve entities somehow. I have no idea how to use the classes, like GrabItems or CreateNewMesses. Who knows if either of those do anything? Oh, and making an item or appliance? No idea.

As you can see IL code is not exactly human readable, and it's also quite verbose. If you want to have an idea of how your code looks like in IL you can use a decompiler tool such as JustDecompile or ILSpy.

I've been using JustDecompile and dnSpy. Remember that if it's programmed in, let's say, c++ or c, it's not that simple to reverse engineer. Simple C# .NET programs should be fairly easy to reverse engineer.

It's .NET code, so you can disassemble it or view it with a tool like Telerik's JustDecompile.

Looks like it hasn't been updated for years (at least according to their GitHub repo): https://github.com/telerik/justdecompileengine