i read the other thread and purposefully did not respond to your advertisement. i barely respond in any of these threads (ie: octopus, ahk, hkn) unless there is something that could get an unsuspecting user in trouble.

to say that you have access to in-game memory, but you promise to be good... is just funny. you have OBVIOUSLY crossed the line once you have access to their applications memory. i would even go as far as to say that glider did nothing wrong as it behaved as any innerspace mod would. the root problem wasn't the type of mod but the mechanism that breached the line in the first place. (i would have to read the EULA to see if you violate any reverse-engineering wording by reading the binary and acting on it)

if you are saying that it is perfectly acceptable with Blizzard for your application to be in the same memory space as wow, i would love to hear your justification.

for those that are unaware, having full access to blizzard's in-game memory could give InnerSpace various in-game knowledge, like passwords, locations of players, npcs, as well as resources. depending on wow's messaging protocol and client/server model, he could even introduce packet drops that could minimize damage, decrease timers or increase damage output (although i'm fairly certain blizzard checks their timers on the server)

to say that Blizzard would be fine with that is just funny.