Tycoon !!top!! — Dungeon
Adventurers naturally prioritize walking through more expensive doors. Use high-tier doors to seamlessly funnel the traffic of heroes down specific, high-profit paths.
: The primary goal is to maintain a balance—killing heroes for while keeping them alive long enough to spend on potions and services [5, 18]. Research & Progression Dungeon Tycoon
to reach an ending, though players can continue building or start new runs. Critical Reception & Development Status The game is available on . Its reception is "Mostly Positive" (approx. 78%), but recent feedback has been mixed. Research & Progression to reach an ending, though
Late-game crashes have been reported when dungeons become large [12, 21]. Some players find the financial balancing difficult early on [7]. Common Requests 78%), but recent feedback has been mixed
In , you trade the typical role of a brave hero for that of an evil entrepreneur. Your goal is to build a thriving dungeon business where heroes are the "customers" you must satisfy before—ideally—relieving them of their gold or souls. Core Gameplay Mechanics
I can imagine it took quite a while to figure it out.
I’m looking forward to play with the new .net 5/6 build of NDepend. I guess that also took quite some testing to make sure everything was right.
I understand the reasons to pick .net reactor. The UI is indeed very understandable. There are a few things I don’t like about it but in general it’s a good choice.
Thanks for sharing your experience.
Nice write-up and much appreciated.
Very good article. I was questioning myself a lot about the use of obfuscators and have also tried out some of the mentioned, but at the company we don’t use one in the end…
What I am asking myself is when I publish my .net file to singel file, ready to run with an fixed runtime identifer I’ll get sort of binary code.
At first glance I cannot dissasemble and reconstruct any code from it.
What do you think, do I still need an obfuscator for this szenario?
> when I publish my .net file to singel file, ready to run with an fixed runtime identifer I’ll get sort of binary code.
Do you mean that you are using .NET Ahead Of Time compilation (AOT)? as explained here:
https://blog.ndepend.com/net-native-aot-explained/
In that case the code is much less decompilable (since there is no more IL Intermediate Language code). But a motivated hacker can still decompile it and see how the code works. However Obfuscator presented here are not concerned with this scenario.
OK. After some thinking and updating my ILSpy to the latest version I found out that ILpy can diassemble and show all sources of an “publish single file” application. (DnSpy can’t by the way…)
So there IS definitifely still the need to obfuscate….
Ok, Btw we compared .NET decompilers available nowadays here: https://blog.ndepend.com/in-the-jungle-of-net-decompilers/