I'm the dev of "dualChoc".

[Lax]

There is no hooking or calling of any code. The software simply reads the chatbuffer from the wowclient. You just wrote what it does. It types the text into the chatwindow (exactly the way other dualboxing software works. The difference here is that it does not read the keys coming from another dualChoc app but from the chat.)

Thanks for clearing that up for us.

I believe you are wrong about how you think (or at least how you say you think) other dual-boxing software works. Your site says you can do things like this:

/t PlayerName #cmd /assist Playername

... which legitimate dual-boxing software accomplishes /assist Playername by emulating keystrokes to WoW binds -- it would be very unreliable to execute a command like "/assist playername" by emulating typing. I don't exactly believe this is what you are doing.

Also, it is very much against Blizzard's policies to read the chatbuffer from the WoW client memory. Any time you need information about WoW-specific memory addresses or data structures to accomplish your goal, you can bet that it is NOT within the rules of the game, and has no place on a forum like this. As someone previously mentioned, they disabled the ability to do similar things via addons, and there are "blue posts" stating that if they removed the ability for an addon to do it, they do not want you to do it.

I don't believe this is a) a real application regardless of whether it is allowed or not, nor b) allowed as per the Terms of Service. If it was doing this and only this, it would not come in the form of 2 encrypted 3mb executables with protection against running in a Virtual Machine. It may even do what it claims to do in order to hide its real purpose. I wouldn't trust it one bit.

The "endorsed by Blizzard" bit is hugely misleading especially with what the app claims to do, and I believe this is simply a tactic to get as many people trying it as possible under the false pretense, to install whatever malware is packaged inside. I know at least one person has sent an email to hacks@blizzard.com about this, and I would recommend anyone else do the same.

[Svpernova09]

If you are reading chat buffers from the client. Then you are in violation of the ToS.

From: "World of Warcraft/Data/enUS/tos.html"

2. Additional License Limitations. The license granted to you in Section 1 is subject to the limitations set forth in Sections 1 and 2 (collectively, the “License Limitations”). Any use of the Service or the Game Client in violation of the License Limitations will be regarded as an infringement of Blizzard’s copyrights in and to the Game. You agree that you will not, under any circumstances:

C. use any unauthorized third-party software that intercepts, "mines", or otherwise collects information from or through the Game or the Service, including without limitation any software that reads areas of RAM used by the Game to store information about a character or the game environment; provided, however, that Blizzard may, at its sole and absolute discretion, allow the use of certain third party user interfaces;

[zanthor]

There used to be an addon called whispercast which would let people whisper you a buff and you'd then buff them with the correct spell. Quite a while ago Blizzard broke the function that let people do that with addons, so I don't see how a piece of software that enables this is going to be ok with them.

I remember that. Now in whispercast it 100% automation. Remember dualchoc only triggers your text. Converts it from tell into chat. So you can for example just submit a "#cmd Hello" and it'll write "Hello" in whatever channel is active. This means for /cast you would 1st have to manually target someone using /target, then use "/cast whatever". There is no automation - i assume you can do the same with other programs, the difference is you have a more complicated setup to do so. (Making tons of macros.)

Seriously. All the software is doing is allowing you to control another character interface - just through the chat itself instead of tcp/ip or p2p. It might be the best idea to get a blue statement on the official forums for this. I guess everything else doesnt really matter...

Actually Whispercast had to have a button push (hardware event) and it used the whispers to Queue up the spells it would cast. It was simply a logic trap... a logic trap that blizzard removed completely from combat situations because they didn't want it used this way.

[Xzin]

Sorry but this software appears at first glance to be so sketchy, I wouldn't even run it under a VM.

[keyclone]

It is bannable to read or modify WoW game memory, including the in-game chat interfaces. Blizzard would certainly not approve of software that does that.

pot meet kettle. just laughable.

it's also bannable to use loops, delays, or multiple keys from one key press.

of course, the last ban wave happened months after ISxwarden /wowglider had been used for months... all the time the users were being told how 'safe' they were, since your software hid glider from wow.