Re: How to Protect your python log
2 hours ago, MADOFOCS said:The best way is to create a limited user and start WoT with the limited user + make python.log read only. If you start the WoT as limited user, they wont be able to scan the whole pc + memory. I think best solution is to get the mods out of the res_mods and WoT directory and make an executable. If WoT is started with the limited user and you denied the access to the mod.exe, they wont be able to scan the memory or even get access to the file. This is working turbohud in diablo3 for the last 3 years and blizzard has Warden Anti-Cheat and is a real company not comparable to WG.
Last time last year they implemented a anti cheat routine and many player were banned, even if they play without mods and had replays from the last 6 month, WG said the routine is fine and is working as intended, but after 2 weeks research, they have to admit, that the routine is faulty and gave the banned players gold and premium time. I personally think that it wont be better this time.
How is a company to create an anti cheat engine, if they have not managed to fix bugs in 5 years?
With a limited user, you have to allow the game to run and all non exe mods are loaded by the game in the games memory allotment. If they were not, they would not run at all. As such, the game can read anything in its memory space.