HelloHello

I'm "into developing stuff for commercial use". That's my day job. I may have been doing it longer than you have been in school. Since requesting a handle on the System.Process object does not scan memory, not that any of you are legal experts, I consider it pretty unlikely that a court of law would find it to be scanning memory. Regardless, you should never want to rely on the idea that people at GGG or at any company have never used a common piece of Microsoft functionality that is undetectable without a lot of reverse engineering, possibly without the leads even knowing about it, simply because it's theoretically illegal in your opinion. Think about every hole or weakness in the bot, whether it should or shouldn't be found by the devs because of legal issues or whatever, as being sort of like fucking somebody without a condom. It's a bad risk. THIS is a bad risk. This bad risk ought to be very easy to remedy. It's extremely easy to change the window title and process description. What do you end up with when you take dozens of bad risks? When you don't stop taking bad risks? A bad outcome. Y'all are too nonchalant about these little bad risks. They pile up into a big bad risk. Good luck.

GGG doesn't disclose how they detect botting. What % of the user base would you guess runs a windows program titled "Exiled Bot" that isn't this bot?

The OS voluntarily returns a handle on all the processes, and this is part of the OS design - processes are visible and accessible to other programs. The Process object in the .NET library does not expose the global memory state of the process, but it does expose facts like the window title. I'm sure there are similar Microsoft functions for C++. This can be alleviated by not running the bot as an ordinary application, e.g. thread injection into a third program, and THEN GGG would have to forcefully inspect your memory in more invasive ways, but I'm talking about a function that requires no administrative privileges to use and the OS allows, hell, Microsoft implemented by design. It doesn't make sense that this is clearly illegal unless you actually have a specific court case in New Zealand or a statement from GGG.

Guys, Really freaking easy to detect this program. This is really scary. C#: Returns true, and worse yet, if I As soon as the application gets focus, the application reverts its title back to "Exiled Bot". I literally can't make the application not trivially easy to detect by constantly polling and resetting the window title even if I try. Also, do you have / can you expose a method that allows allow me to invoke Exiled Bot's main program with no UI as a console thread I own? The only way I could feel remotely safe about this right now is if I could run it as a thread with arguments and no window, and then do something after spawning Exiled Bot as a thread that my process owns.