Can be easily solved. For that you need somebody who is experienced in Computer Forensics & Reverse Engineering. Use Sandboxing Application (ProcMon is fine too) to trace all WoW's (and its services') SysCalls (System Calls) and then just limit WoW's (and its services') operation limit to the WoW's root directory and appdata+programdata+userdata folders, while ignoring/blocking/giving fake responses to the syscalls that information beyond your permission - make sure that it applies not only to WoW's executable, but also to all WoW's background services that can even sit on Kernel level (haven't checked personally).It saddens us to close these services, but the recent advancements from Blizzard's side are only possible because of their decision to compromise the privacy of their players. While WoW runs, the game is continuously scanning the user's computer with the capability to send back exactly which applications the user is running, and in some situations even going as far as sending back window titles of any window on the computer. These things happen even if WoW is running in the background, and even without logging in to a character.
Sorry for digging up an older thread here, but would the devs consider open sourcing the bot before fully closing the doors so other devs can use it as a learning platform?
It's probably stipulated in the lawsuit that they can't.
I don't think they lost the lawsuit I think they just choose to stop producing the bot.
And in the original post, bossland says, "It is not quite over yet, but we need to adapt to these new circumstances to even stand a chance of continuing in the future."that is true
Why not "hook" in another process. I know several CS bots that hide behind notepad or any programm the user choose? Works like, start programm of your choice, start bot and tell him what process he will hide behind, start wow.. hf ?