Quote from: terion on August 11, 2020, 10:33 AMbtw, WA's warning message should be made more clear about the cause of error 0x7E to avoid confusion.
The error message shows:
1. The module that failed to load
2. The exact function call that failed
3. The numeric error code reported by your operating system
4. The localized error message for said error code, as provided by the operating system
5. A most likely explanation of the error (also localized to your language), which is true for this particular case
6. Advice to the user, which is again actually relevant here
How could it possibly be even clearer? Or do you really expect the game to implement a Windows PE parser to scan the dependencies of every module it loads? And all that, just because you 1) chose to use the CRT, 2) chose to link to the CRT dynamically, 3) decided to not include the runtime with your module, and 4) failed to communicate to your users what the installation procedure and dependencies are?
I think such an attitude gives a bad name to the entire WormKit authors community, and it would be good to see less of that.
BTW, I don't understand why you use CreateToolhelp32Snapshot / ReadProcessMemory etc. You know that WormKit modules run within the same process as the game itself, right? You can access the memory directly. And, if you really need a handle for some reason (soft fails on invalid addresses?), you can use GetCurrentProcess instead of tlhelp32.