dnSpy VS eShopOnContainers

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.

The eShopOnContainers is pretty popular, have you seen it yet? https://github.com/dotnet-architecture/eShopOnContainers

so I was exploring eShopOnContainers a little bit, more specifically the messages queues part and it made me wonder how is it possible to ensure data consistency across microservices when using them. If I'm not mistaken this isn't even shown in the eShopOnContainers examples.

For an example of an aggregate if you're unfamiliar - https://github.com/dotnet-architecture/eShopOnContainers/blob/3169a933447f1013c069e2cad2805c5de1ce9fbf/src/Services/Ordering/Ordering.Domain/AggregatesModel/OrderAggregate/Order.cs

You can check out eShopOnContainers as a reference architecture if you want, but (assuming this is meant to be somewhat of an ad hoc solution rather than a paragon of software engineering) I'd minimize the number of deployable assemblies (1 + tests if possible) and avoid Docker, again unless you have a specific reason to use it.

For K8s, it has a whole directory with deployment scripts. https://github.com/dotnet-architecture/eShopOnContainers/tree/dev/deploy/k8s

Checked the eshop on containers which uses EF for writes with DDD. Queries uses Dapper with raw sql. https://github.com/dotnet-architecture/eShopOnContainers/blob/dev/src/Services/Ordering/Ordering.API/Application/Queries/OrderQueries.cs

Maybe Microsoft’s eShopOnContainers reference system?