Duel Boxing - Windows 7

[CaffeineAddiction]

Hello, recently purchased a new PC with the intention of getting into duel boxing. I have been playing on a Mac for the last year or two, and have a few issues im trying to work out.

Windows 7 Compatibility (can anyone confirm if these work on windows 7):
Game Commander Pro
Key Clone
Any support for n52 (open source, closed source, or third party)
Any support for Ergodex DX1 (open source, closed source, or third party)

Does anyone know of a piece of software that allows for advanced macro functionality that would be even close to what ControllerMate v4 for OSX provides? Aka not just key presses and repeat timers, or recorded strings of key presses ... but actual math and logic w/ binary toggles, AND, OR, NOT functionality ... basically http://www.orderedbytes.com/controllermate/ but for windows instead of mac.

Finally, does anyone have any information on Bliz's views on programs such as Autoit, Vbscript, Python scripts to allow for the replication of "Rotations" that use Priority systems based on times a spell/button was last used/pressed.

[Jafula]

Finally, does anyone have any information on Bliz's views on programs such as Autoit, Vbscript, Python scripts to allow for the replication of "Rotations" that use Priority systems based on times a spell/button was last used/pressed.

My 2 cents:

I don't know about Blizzard, but my guide, is that if you can do it in game, using the macro system, then its _probably_ okay to move that functionality out.

I don't think you can count how many times a spell/button was used in game, so a system like that will probably violate some of Blizzards rules.

[MiRai]

What is with all of those colors?

[kate]

My 2 cents:

I don't know about Blizzard, but my guide, is that if you can do it in game, using the macro system, then its _probably_ okay to move that functionality out.

I don't think you can count how many times a spell/button was used in game, so a system like that will probably violate some of Blizzards rules.

The hard and fast rule that I have heard time and time again is: Only one action per button press with anything that isn't an in-game macro or addon.

So, for example, you can't have an outside program send keys 2-5 every time you press the 1 key so that it fires off whatever ability isn't on the GCD.

As to a tool, AutoHotKey does have the ability to handle programming logic. It obviously can't hook into the WoW client and do something like "when I press 1, if art of war is up cast exorcism, otherwise cast divine storm" but you can have it do conditionals and other stuff. I really didn't do much more with it than have it do 1:1 broadcasting of certain keys in game, but I did have it set up to loop through a set of questions about which screen was the master, which was the slave, which was the healer, etc., so that it would send different keys to each client.

[Eloxy]

To the OP:

I know im sounding like and ass here, but plase...its called DUAL boxing or quad boxing. Dont say duelboxing plz dont =(

[kate]

To the OP:

I know im sounding like and ass here, but plase...its called DUAL boxing or quad boxing. Dont say duelboxing plz dont =(

I'm dying from irony poisoning here. Were your numerous spelling, punctuation and grammar errors intentional?

Just having fun!

[Ualaa]

Just about all of the boxing software options are Win7 compatible.
You'll want a 64-bit version of windows, so you can use more then ~3gb of ram.

I'd recommend taking a look at IS Boxer, as far as boxing software goes.
It does as much as any other software, and far more then most of the options.
For example, you can use most of the devices like an n52 or G15 etc as input devices for its mapped keys.



Keypresses or mouse clicks are fine to broadcast, but if you use loops or automatic re-presses on timers, you'll find yourself eventually banned from warcraft; even if you found something which gave that functionality, you would not want to use it.

You can do a priority system, with the wow in game macro system.
Take a look at click castsequences. Your software is broadcasting one keystroke repeatedly, and your consistent "spam" speed combined with commas (no action, in the macro system) determine how long until the spell is recast based on the number of commas.
Doing this software side, where it automatically recasts at a point, on its own is not a good idea.

The general rule of thumb, the macro/script cannot make decisions for you.
It has to act, according to how it was configured.
You can use:
/cast [help][help,target=targettarget] Heal Spell; [harm] Nuke Spell
Although the macro will do one thing for a friendly, and redirect to the hostile's target if the main target is hostile and its target is friendly, or if both conditions fail then cast a harmful spell on the target... it makes no decisions for us and functions exactly as expected each time.
The macro system is flexible, in a lot of ways, but cannot use if/or/then type logic.

[Eloxy]

I'm dying from irony poisoning here. Were your numerous spelling, punctuation and grammar errors intentional?

Just having fun!

go away! ^^