dnSpy VS x64dbg

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.

I have never heard anyone say anything good about the Visual Studio debugger before. Now, I'm not a Windows person but I'm not gonna argue for gdb or lldb here. RemedyBG and x64dbg are the two debuggers I've heard good things about though I've never used them because, again, not a Windows person.

[1] https://remedybg.handmade.network/

[2] https://x64dbg.com/

I'd help you out but because of circumstances I have no laptop with me. You need x86/x64 debugger to do this. This one for example Find a registration procedure and look for possible brenching to other parts of code in assembly. It's probably somewhere in the beginning. Exclude code validation and export new program version.

One interesting thing you can do is download an app like https://x64dbg.com/ or cheat engine, which will let you see the memory. You can look at the process for something you’ve made and explore it. Log a memory address from your app then go find it in the tool and interpret the bytes as an integer. Find a string and see how that works. Find a pointer, read the address it’s pointing then go look at that address. You start to see how different containers store data. I find it fascinating.

If you want to also do dynamic analysis (debugging) you can use https://x64dbg.com.

close origin and download this debugger https://github.com/x64dbg/x64dbg/releases

.exe is a complex format and not something you're going to extract raw instructions from using a hexdump. What you need is a "disassembler". For Windows I'd recommend x64dbg.

Patch the DayZServer_x64.exe, change "test al, al" to "cmp al, 2". i used x64dbg (https://x64dbg.com) a good video for the whole process: https://drive.google.com/file/d/1F1A0lpumREPXtVeoTMq1HiEnvaZp-NUU/view