This is very hard to directly get you head round, so 'decompilation tools' are then all assistants that help the manual process of understanding the structure of the program. We just perform the minimal processing to get the human readable form of the assembly instructions that make up the binary. Instead what we actually do is 'disassembly'. You could infer this based on your knowledge of how compilers usually work, and how developers usually develop but it's all guesswork. Function names are one things that's mentioned, but the very structure of the program (which functions are in which classes, etc.) is lost. No automated tool exists that allows you to do that - too much information is lost in the compilation process. That term implies that you can get your compiled binary and turn it back into C++. It's a very new library, so it shouldn't have 15 years of legacy cruft in it.Ĭalling it "decompilation" is misleading. But this is a recent development the only games so far that use Jomini are Imperator and CK3. None of this is in the Clausewitz engine itself.įunny thing though, they actually did decide (relatively) recently to centralize a lot of basic GSG functionality in one place so they don't have to keep copying-and-pasting code. The reason why all Paradox games have so many things in common-a map-based UI, the scripting language, everything else that makes a GSG a GSG-is that game code gets copied and pasted from game to game as they start new projects. It just does what every other game engine does, none of the actual game mechanics are coded into the engine. It's actually a running joke on /r/paradoxplaza that every time you mention Clausewitz, Meneth (or one of the other developers) pops up to explain this. "The core engine" doesn't do what you think it does.
0 kommentar(er)
