I didn't speak with a GM and...

Blizztard will not tell you what program will or will not cause your account to be banned or suspended.


I have done some research.

I have two boxed two accounts for over a month using Keyclone. I paid for two copies and I was impressed with the work.
Keyclone+KavoomKM+twoboxtookkit
I next checked out HotKeyNet. I have been an active beta tester for Fredie. And again, I am happy to give kudos to the man. HKN is a fine program.

Here I asked this community about IS and was shut down fast. Read it for yourself. InnerSpace is a dirty word around here.
Keyclone+KavoomKM+twoboxtookkit

I have spent months testing these three multi-boxing solutions. No bans, no suspensions, no problems.

You can configure HKN to break the EULA just as you can configure InnerSpace to do the same. I firmly believe that it is up to the user to use these tools responsibly.

The problem that I have with some of you guys is that you do not know the difference between a bot, a script, an InnerSpace extension and InnerSpace itself.

Learn the difference before you show the world how damn stupid you are.

-j

/pops his head out of a hole

/wave Lax

/avoids large flamethrower

Someone asked: Are you the "real" Lax? And with the real Lax I mean the one that writes Innerspace and also writes the warden detection bypassing mods?

Quote:

---

Originally Posted by 'Lax',index.php?page=Thread&postID=133370#post1333 70

Don't ask me for any favors when your world is flipped upside down. I would love to explain what I know and can't disclose that you don't know and wouldn't believe even if you heard it, but as I have suggested in my previous posts, it will become apparent in the coming months. You can take my word on that

to be a part of a community that relies on technologies that I helped pioneer and have been innovating in for a long time. Who do you think people come to when they have a question related to developing these things (e.g. Octopus), and where do you think these other developers got ideas for features like Picture-in-Picture?

---

I've seen posts by Lax before and this is classix Lax egotism so I've no doubt it's the real thing, I wouldn't trust anyone who makes such an overblown issue out of his 'product' regardless of it's thinly sliced 'legality'.

If Lax sold replica guns, tools for converting them to live, and ammo all 'separately' and then claimed that he hasn't got anything to do with how people use them he'd be laughed out of court. Just because Blizzard hasn't kicked his butt into court doesn't mean that what he creates is genuinely and incontrovertibly legal.

http://www.lavishsoft.com/forum/view...t=warcraft+ban
Inner Space can indeed get you banned from various games depending on what you do with it. I don't know of any besides World of Warcraft that have banned for "vanilla" Inner Space. You usually have to be trying to do something they don't like in order to get banned, and use of Inner Space itself doesn't necessarily meet that criteria.

http://www.lavishsoft.com/forum/view...t=warcraft+ban
eqJoe going off about Blizzard being stupid for banning for vanilla IS.

Since July 2007...
http://www.lavishsoft.com/forum/view...t=warcraft+ban
Inner Space has a much higher chance of banning, with or without ISXWoW. Due to recent aggression from Blizzard, Inner Space will not allow you to run WoW without having ISXWarden to protect you from detection. There is no public stance on this from Blizzard, but I do believe that while they frown upon usage of Inner Space itself, they have generally not banned for it alone -- they certainly COULD if they wanted to. When ISXWoW is in the picture, there is no question whether it is bannable or not

All said and done, IS wont run WOW Vanilla. It REQUIRES running an extension that hides it from Warden...

So, it sounds to me like you can't run WOW using IS Vanilla, and haven't been able to for 1.5 years now... and I'd say if you NEED to run something to HIDE IS from WoW, then you probably shouldn't be running it...

Quote:

---

Originally Posted by 'zanthor',index.php?page=Thread&postID=134013#post 134013

http://www.lavishsoft.com/forum/view...t=warcraft+ban
Inner Space can indeed get you banned from various games depending on what you do with it. I don't know of any besides World of Warcraft that have banned for "vanilla" Inner Space. You usually have to be trying to do something they don't like in order to get banned, and use of Inner Space itself doesn't necessarily meet that criteria.

http://www.lavishsoft.com/forum/view...t=warcraft+ban
eqJoe going off about Blizzard being stupid for banning for vanilla IS.

Since July 2007...
http://www.lavishsoft.com/forum/view...t=warcraft+ban
Inner Space has a much higher chance of banning, with or without ISXWoW. Due to recent aggression from Blizzard, Inner Space will not allow you to run WoW without having ISXWarden to protect you from detection. There is no public stance on this from Blizzard, but I do believe that while they frown upon usage of Inner Space itself, they have generally not banned for it alone -- they certainly COULD if they wanted to. When ISXWoW is in the picture, there is no question whether it is bannable or not

All said and done, IS wont run WOW Vanilla. It REQUIRES running an extension that hides it from Warden...

So, it sounds to me like you can't run WOW using IS Vanilla, and haven't been able to for 1.5 years now... and I'd say if you NEED to run something to HIDE IS from WoW, then you probably shouldn't be running it...

---

I got your PM but to clear this up for everyone else: Inner Space does not require ISXWarden, or my site would not be promoting IS for Multi-boxing, particularly without informing the readers that another tool is required and they would have to go elsewhere to get it. As I've explained in this thread several times, ISXWarden will automatically load if the user had gone out on their own, found and downloaded and installed it. Otherwise, ISXWarden is not required, does not come with Inner Space, and will not get loaded, etc.

The bans referred to are not relevant to the state of Inner Space. The point is that if you're not trying to hide Inner Space with ISXWarden, you obviously have nothing to hide. All I can do is reiterate what other people like Suribusi and eqjoe are saying: Inner Space vanilla is not resulting in bans and both report using it for months. On the other hand, if you were to try to use ISXWoW, you would get banned within 20 minutes from that I'm told.

RobinGBrown:

Quote:

---

I've seen posts by Lax before and this is classix Lax egotism so I've no doubt it's the real thing, I wouldn't trust anyone who makes such an overblown issue out of his 'product' regardless of it's thinly sliced 'legality'.

If Lax sold replica guns, tools for converting them to live, and ammo all 'separately' and then claimed that he hasn't got anything to do with how people use them he'd be laughed out of court. Just because Blizzard hasn't kicked his butt into court doesn't mean that what he creates is genuinely and incontrovertibly legal.

---

Classic egotism? I'm sharing factual information and providing reasoning, and when someone responds and says that I'm claiming it's completely safe, and I respond and say that's not what I said, I said that the level of safety will become apparent in the coming months, that is your basis for calling me egotistical? The person I was replying to thought I said it's safer than the other available solutions.

And I don't understand saying that I'm "mak[ing] such an overblown issue", I was only trying to correct the misinformation that was here on this thread, it's other posters making it "overblown" (not to mention the overzealous guy that says he wont post on the forum because he thinks that Blizzard will overzealously ban people for posting on forums where I post).

And you're missing the point with your analogy of me "Selling guns, tools for converting them, and ammo". I personally take the blame for ISXWarden. Inner Space is owned by a company. Blizzard could block ISXWarden and hold me personally liable, but that has no bearing on Inner Space itself, and ISXWarden existing has no bearing on whether Inner Space violates the Terms of Service. If Blizzard were to take action, it would not involve Inner Space itself. I have had these kinds of conversations with my legal counsel, and I would really trust their opinion long before yours, sorry (call me egotistical for listening to my lawyer please <3 ). My ISXWarden is also not being distributed currently in the first place, so even if the general public wanted to cheat, they would have to find someone willing to give them an ISXWarden that was written by someone else entirely, and good luck finding that.

Quote:

---

Originally Posted by 'Lax',index.php?page=Thread&postID=134039#post1340 39

I got your PM but to clear this up for everyone else: Inner Space does not require ISXWarden, or my site would not be promoting IS for Multi-boxing, particularly without informing the readers that another tool is required and they would have to go elsewhere to get it. As I've explained in this thread several times, ISXWarden will automatically load if the user had gone out on their own, found and downloaded and installed it. Otherwise, ISXWarden is not required, does not come with Inner Space, and will not get loaded, etc.

The bans referred to are not relevant to the state of Inner Space. The point is that if you're not trying to hide Inner Space with ISXWarden, you obviously have nothing to hide. All I can do is reiterate what other people like Suribusi and eqjoe are saying: Inner Space vanilla is not resulting in bans and both report using it for months. On the other hand, if you were to try to use ISXWoW, you would get banned within 20 minutes from that I'm told.

---

Thanks for the clarification, I was just about to link you what I had found per your e-mail request and found you found what I found... these forums are running like dog squeeze recently...

lol, so I guess it went off topic a little.

I got access tor my account back, no real explanation except they made me change my password cause they said my account was not secure. So I guess someone else got on my account and was using some sort of automated script for something.

Anyways, you guys have fun talking about innerspace :) I'm back to leveling

Congratulations ncliff, nice to hear the problem has been resolved. :)

Hi all,

My 50 cents in this interesting thread..
Hope I don't piss you off again Lax. I don't really care, but FYI it isn't my aim to do so. I'm a straight shooter..

Your system DOES use stealth you know. Your system injects several DLLs in a target process.
I never looked in detail but I think you are de-linking the modules, or just doing custom mapping to avoid having them on processes list to begin with.
And I think you are messing with the headers to hide from Walks with VirtualQuery() et al.

Anyhow maybe this is a problem. This is a third party software either modifing, or adding something in it's space.
But then again, so are these other programs that are doing the screen splits, PIP, etc. (like "Maximizer"), as they typically use DirectX hooks.
(Humm, maybe it can be done at a kernel level a layer or two above process spaces).

One could make one of these key broadcasting programs with out any of this of course if they didn't want all the fanciness (the screen splitting stuff, overlay GUIs, etc).
Just use an external process using standard Win32 APIs, don't have to be in the processes space IMHO.
If I'm not mistaken something like your "ClickBoxer" could just be a separate window rather then an overlay.

How about just getting an official word from Blizzard, on whether or not using WOW with "Inner Space" is okay?

Quote:

---

Originally Posted by 'Sirmabus',index.php?page=Thread&postID=134161#pos t134161

Hi all,

My 50 cents in this interesting thread..
Hope I don't piss you off again Lax. I don't really care, but FYI it isn't my aim to do so. I'm a straight shooter..

Your system DOES use stealth you know. Your system injects several DLLs in a target process.
I never looked in detail but I think you are de-linking the modules, or just doing custom mapping to avoid having them on processes list to begin with.
And I think you are messing with the headers to hide from Walks with VirtualQuery() et al.

Anyhow maybe this is a problem. This is a third party software either modifing, or adding something in it's space.
But then again, so are these other programs that are doing the screen splits, PIP, etc. (like "Maximizer"), as they typically use DirectX hooks.
(Humm, maybe it can be done at a kernel level a layer or two above process spaces).

One could make one of these key broadcasting programs with out any of this of course if they didn't want all the fanciness (the screen splitting stuff, overlay GUIs, etc).
Just use an external process using standard Win32 APIs, don't have to be in the processes space IMHO.
If I'm not mistaken something like your "ClickBoxer" could just be a separate window rather then an overlay.

How about just getting an official word from Blizzard, on whether or not using WOW with "Inner Space" is okay?

---

1. Lots of things inject into target processes. For example, Logitech mice come with software that injects into every process. The simple act of injecting DLLs into a process makes no difference whatsoever.
2. Yes obviously something like ClickBoxer *could* be a separate application. But, that would defeat the purpose. The only reason it's useful to have such a UI is because it is in game. The main purpose of ClickBoxer is to demonstrate the ability and simplicity of its function, not "hey look we have something unique" but rather, hey here is an example of how you can do this, and it is very easy to do.
3. If Blizzard were inclined to do something like that, believe me I would. Assuming they're not, you'll just have to take the word of people using the software, just like with every other program used with World of Warcraft.