Quote:
Originally Posted by Aepiath
Die Probleme von damals mit dem Launcher sind behoben und falls irgendwelche auftreten wissen wir direkt was das Problem ist und können weiterhelfen. Außerdem blockiert er LCPE, somit ist Dupen nicht möglich.
|
It may prevent LCPE however if the launcher is responsible for
stopping it then it's really only mitigating it and not really stopping it. The only thing really stopping LCPE from working is the fact that I don't mess around with LastChaos anymore.
I'm not sure what you are checking for but it could be simple.
Quote:
1. Enumerating processes, checking just for the Injector process.
2. Enumerating windows to check for titles names.
3. Checking for loaded modules inside of the client process.
4. Checking for any JMP's at the original functions.
|
The last two I doubt if the launcher handles everything as you would need consistent access from within the process. Opening a handle and going from there would only be an extremely weak way of parsing for that bit of information.
The list could go on and on. However as noted already, what stops people from just downloading a generic EP3 client and copying over the catalog data then abusing the item mall? You would need to have a brewed up anticheat that runs at client runtime along with at least some generic form of prevention like changing the login opcode so that no other clients will work with your server (would require server side patch on both login + game servers). Otherwise if the launcher does all the magic of just running code (my guess) or injecting code. Someone else could inject their code before yours, which in turn could detour LoadLibraryA or whatever you are using to inject your code and stop it before it even starts.