NDepend Blog

Improve your .NET code quality with NDepend

Far Cry 3 Complete Collection -pc- -espa... Access

If you want the definitive Far Cry 3 experience on PC with all story DLCs and don’t mind the old-school graphics, this is the version to buy. Just manage expectations for multiplayer and double-check your language settings if Spanish is essential.

Solo players, Far Cry newcomers, Spanish-speaking gamers who can handle minor DLC text issues. If you meant something else—like you wanted the actual review written in Spanish —just let me know and I’ll translate it fully. Far Cry 3 Complete Collection -PC- -Espa...

Assuming you want a about the Far Cry 3 Complete Collection on PC (but with attention to Spanish/ES features), here is a concise review: Review: Far Cry 3 Complete Collection (PC) If you want the definitive Far Cry 3

It seems your message got cut off—specifically the "-Espa..." part, which likely refers to (either the review itself or the game's localization). If you meant something else—like you wanted the

Comments:

  1. Ivar says:

    © 2026 Nova Tower

    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.

  2. David Gerding says:

    Nice write-up and much appreciated.

  3. 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?

    1. > 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.

  4. 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….

Comments are closed.