If you aren't injecting(don't really see why you would) then you don't need much protection. Warden/WoW doesn't scan window titles, I would have the app run WoW as guest account just as a precaution though.
If you aren't injecting(don't really see why you would) then you don't need much protection. Warden/WoW doesn't scan window titles, I would have the app run WoW as guest account just as a precaution though.
Well, nevermind then. You don't really need anything at all. Just keep it private.
I don't intend to keep the bot private... I want it to be available for anyone who wants it. Just not the code.
Then you have to worry about getting detected.
Yup. I was thinking of a few options I could explore. I know most of these are extreme overkill, but hear me out.
1: The setup program that installs the bot will pad the bot executable with a random amount of garbage bytes at the end of the file to alter the checksum.
2: The setup program that installs the bot will install it to a randomly named program files folder 8-24 characters long. It will also randomly name the executable to be 8-24 characters long.
3: The executable will "unpack" itself, creating a new randomly named executable 8-24 characters long, also padding this executable with a random amount of garbage bytes to alter the cheksum.
4: This newly created executable will be unique in name and size each time the bot is run. It will have a random title bar name generator that will re-name the title bar of each window in the bot when the window is shown. It will be different every time the window is shown. (Already done).
Feel free to add to this if you have any more ideas. Thanks!
1. Won't work. Warden uses a relative checksum not an overall checksum for modules (please correct me if I'm wrong kynox), so it will hash a small section, not the entire thing. Besides, it only hashes DLLs loaded by WoW, not binaries outside its address space, so its a moot point anyway.
2. You're joking... right?
3. See 1 and 2.
4. See 1, 2, and 3.
(Sorry for the late post.)
I believe your understanding of LUA is flawed -
you can have an addon do all of the 'getting' for your application.
LUA's are restricted so you can't cast a spell, for example, from inside the scope of a logic check. Like: if ( myHealth < 30% ) cast heal, etc.
But, you can have your external program call GetLowestHPRaidMember() (which is an lua function) and it will make your life a lot easier. That function can have logic checking like, are they alive and within range, etc.
Then, just have the program cast a heal spell (if auto self-cast is disabled, the cursor asking you to target someone should come up) send the ID of the player in question.
Oh also, how is your development going now? Do you have any questions or need any help? What programming language are you doing this in?
From Apoc: Don't necro post, and don't double post.
Last edited by Apoc; 03-14-2009 at 03:21 AM.