sourcelink VS dnSpy

The premise of the tool seems very useful: edit debug symbols and assert messages so that source code can be found by debuggers. But this description does not make it clear how this tool accomplishes the whole task:

> Why not fix the binary coming out of the build cache, so it points to the absolute path of the source files?

What is the absolute path? If you had a virtual file system that allowed you to construct a path to any file at a given commit, this would work great. But who does that other than Google? Or if you agree that every developer will check out the same source code repo at the same path, but the you have to have the right commit checked out.

Ideally you would want your binary to point back to your code repo, like SourceLink does.

https://github.com/dotnet/sourcelink

Reference https://github.com/dotnet/sourcelink/tree/main/src/Microsoft.Build.Tasks.Git

The tooling isn't quite there yet, but between SourceLink and EmbedUntrackedSources, it should be completely reasonable to be able to maintain trust (and eventually, easy, exact reproducibility) for projects that use source generation. Plus, AFAIK, for a package to truly be considered deterministic, all of the sources used for the build either must be tracked by source control, or embedded with the aforementioned flag.

It looks like your NuGet packages is missing symbols (the .pdb files next to .dll files). Symbols let folks map from compiled code back to source code. No symbols make it harder for users to debug your package. I'd recommend using Source Link for your project: https://github.com/dotnet/sourcelink

If you want to enable Source Link for the consumers of your NuGets, make sure you turn on deterministic builds using dotnet build /p:ContinuousIntegrationBuild=true.

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.