Quote:
Originally Posted by sweeper18  Warden can detect whatever is injected or running as a process on the computer...
Injected seems like it would be much easier to detect... WoW can just scan it's own memory looking for things that shouldn't be there, not that hard.
Out of process would mean that whoever develops warden would need a copy of the program and then scan for a string of bytes that is long enough to be unique to the bot.
This is all just what I am thinking of course, never cared enough to open up warden and look at it. |
You shouldn't speak on a subject you don't know anything about.
Warden will not pick up on OB itself. It will pick up on Innerspace. Any application (or script) that uses IS, runs through IS's app domain. Which means, so long as IS is protected from warden, so is most everything else. (Save file edits, and the like)
Also, the difference between injection and non-injection (Glider for example) is the protection scheme. ISXWarden protects people that use IS, and it does it's job very very well.
There was a banwave a month or so ago, but it wasn't caused by warden. (They slipped something into the exe when the 2.4.2 patch came out) That's been fixed.
Also, if you don't know what warden scans (which you obviously don't) don't bother chiming in with some bad information. You'll confuse people into thinking something that isn't true.
i love it good luck with this project and btw dont listen to them fool that are gonna try and rush u go ahead and take ur time so the final result is gonna PWN there whinnie faces.
for kfc lovers out there
