How to have melee automatically "Interact with Target"

[Ualaa]

I've received a couple of private messages, asking about this.

I have updated Example H of my guide, to take advantage of some of the new features in the latest IS Boxer build. Here is the updated example:



The easiest method to do this will be to combine a few techniques -- action target groups, a toggle keymap, and modifying an existing keymap.

First, in the top pane right click on Action Target Groups, and create a "New Action Target Group"; call it Melee. Left click on Melee, then scroll up to and expand Characters. Drag all the toons which you'd like to be able to IWT with, down to our Melee action target group.

Now we create our toggle keymap, specifically for Click to Move. This keymap will have two steps.
Step 1 runs a wow macro (or send the keybind to warcraft for this macro): /console AutoInteract 1
Step 2 runs this macro: /console AutoInteract 0
Step 1 enables Click to Move, and Step 2 disables it.
It might be a good idea to include Pop Up Text, to annouce which state we are in.

Decide which of your FTL DPS Keys will also broadcast IWT.

In the FTL DPS Keymap, click on the Keymap you wish to add IWT to. Right click on the 1 (under Steps), and select "Copy Step to Clipboard". Then right click on Steps for the keymap and "Paste Step from Clipboard".

Click on the Keymap name (DPS 1, for example). Change, "Execute a Step when the Hotkey is" from "released (Default)" to "Pressed or Released".

Click on the 1, under Steps.
In the right pane, under actions left click on the second option "1 -> All".
We're making two modifications here.
a) change the target to "Group (all of): Melee"
b) change the Key Combination to your wow keybind for IWT.

Summary:
By default, an FTL DPS key sends the keybind (on release) to all targets. IS Boxer has the other toons assist the active character and sends the keybind. This behavior remains intact. However, on the press of the key, all toons in our melee action target group, will also press their IWT keybind. And we have a toggle keymap to disable CTM, effectively turning our IWT off.

[Altsoba]

Can never thank you enough Ualaa ^^.

I have to make a compilation of your posts :p

[Shodokan]

Thank you kindly.

[David]

I`m not using IS-boxer yet but I am planning to do so I cannot test this yet.
Does this mean that you stop spamming your IAWT key? You`ll be just spamming skill keys now?

[Ualaa]

Essentially yes.
By spamming normal keys, we send both IWT and the skill.



IWT is a keybind, it is not on the global cooldown.

This is basically creating a keymap within IS Boxer, which will send IWT to the toons of your choice (melee action target group) on keypress down. And, as normal, send whatever key you press to all the toons in your team/set on keypress up.

IS Boxer will of course run the auto FTL, where all of the other toons automatically assist the active toon, and then press the same key.

[David]

Doesn`t that mean that you get 2 actions with 1 keyclick, don`t think that is legal.

[genocyde]

I've been wondering the same thing about having auto assist + IWT on a single keypress. I know by default the FTL IWT key will auto assist my 'active' toon and IWT but you can't macro IWT. How does it accomplish it? Through the ISboxer ingame addon or macros? Is it following the 1 key 1 action rule?

If it is, I think I might create a similar key for my casters for 'auto facing' the target. IWT followed by backwards movement key or something.

[Ualaa]

If you were to glue a penny, across two keys.
And have one as IWT, the other as your DPS key.
Pushing the penny would be one action on your part, but two keys would be pushed.
As far as the game is concerned, it is two inputs; one on key push down and another on key release.

If Blizzard did not want us to do this, they would not have put that functionality into the game. If they decide to not allow this, it is simple on their part -- just remove the functionality which they have given us.


Click on the Keymap name (DPS 1, for example). Change, "Execute a Step when the Hotkey is" from "released (Default)" to "Pressed or Released".

If you don't want to do this as a single keystroke, omit this one step.
Spam the key twice as fast, first press is IWT and second press is your hotkey.

[remanz]

I think IWT is like a wild fire. There is no stopping it now until it has burned all that we know of. Better use it before it is too late.

It is just too tempting to auto it. Auto facing is just too good. I respect Ualaa for his work putting the guides together. But I am afraid blizzard might do something if they see 20+ melee boxing team owning everyone in PVP.

Edit: to be specific, I have asked GM regarding using key-up and key-down actions for my xkeys back in the days. I wanted to press 1 key and have two actions. And he told me not to do it. This might result a ban. Sure they would not bother to catch me. But you don't want to take the chances. After all, you have to be lucky all the time, and all they have to do, is to be lucky 1 time.

[yaki]

It's worse than that, really. If you multibox, you will have GM attention, often, whether you actually get contacted or not. People will report you for "botting" all the time, so even if all you care about is covering your own ass, you'd better make dead sure that there's nothing to find that even smells questionable.

[remanz]

I think the general rules here is anything that a normal, average wow player with standard keyboard mouse input cannot do will likely stir some issues here.

Comparing a boxing slave to a normal keyboard + mouse user:

sending 1 key strokes with 1 key press is fine.

sending 2 key strokes with 1 key press (up and down) is not looking ok. Glue a penny to cover two keys is really not a normal usage. It is still two key presses to the hardware, and the effectiveness is way different than pushing 1 key and 2 action happens. That's like saying I have 6 fingers on one hand and I am pressing more keys.

use external delay for key presses is not looking ok. (you press keystrokes at any speed you want, the keystrokes will get sent out with delay built in). This is discussed extensively when we asked blizzard if it is ok to use G13/G15 macro functions.

[Ualaa]

Well, it would be almost impossible to track what you're doing, unless they look at your IS Boxer configuration file.

In IS Boxer, we send one keybind on key stroke down.
And a different keybind on key stroke up.
The game receives two different keybinds, not our one key.
Our down/up speed will vary slightly.

The same as if you had one finger on F12 and the other on 1.
And were spamming both of them.

If you're uncomfortable with this, as stated previously -- remove the keystroke down or up command.
And just spam the single key, at roughly twice the speed you were doing so before.

[yaki]

You're sending events to their client and their server, it's trivial to log those commands and the time intervals between them, trivial to analyze that log if they ever have cause to - this on top of whatever Warden wants to do constantly.

You're onto "they'll never catch me" as an argument now. Doesn't that tell you something about what you're doing?

[Ualaa]

Well, actually.. I'm not even melee boxing, so I'm not doing anything.



But take for example a "Click Castsequence" which a ton of people here use for dps when boxing.
You are spamming a single key, at as consistent a pace as you can handle.

Adding an IWT into your click is an option.

If you want to stick with one keystroke output per one keystroke input, you can easily make the keymap into two steps.

Then it does exactly what you want it to, and you spam your click twice as quickly.



If you want to stick to this strict interpretation, I would suggest not using any FTL based system, as you are physically only pushing 1, 2, 3 etc on your main screen, but are sending 1 + modifier keys (which you are not pushing on the current client) to the other clients, which lets them know who to assist.

[Mosg2]

Actually, this is specifically not against the ToS. The gist is human action=one action in game. IIRC, it states in the ToS that downclick/upclick is ok.

[yaki]

If you want to stick to this strict interpretation, I would suggest not using any FTL based system, as you are physically only pushing 1, 2, 3 etc on your main screen, but are sending 1 + modifier keys (which you are not pushing on the current client) to the other clients, which lets them know who to assist.

Not relevant. Keybinds are key + modifier.



Actually, this is specifically not against the ToS. The gist is human action=one action in game. IIRC, it states in the ToS that downclick/upclick is ok.

If it does, show me, because this is blatantly against everything I've ever seen on the topic.

[Ualaa]

With a keybind, you are sending Alt + 3, by pressing both the Alt key and the 3 key.

If you only physically push the 3 key, never touching the Alt key.
Then you are sending two keystrokes, with one key press.

Granted, there's no way for Blizzard to know what you pushed, as the software outputs the correct mod (via hotstrings, keymaps etc) to each game, and they only see the final keystroke.
And warden shows that you are using Keyclone, IS Boxer, HKN, GCP etc, which are all fine to use with warcraft.

[yaki]

It's generally not what you use so much as what you do with it. E.g. knives used for cooking, murder.

A hardware event is allowed to one keybind. Using a third party program to make it trigger two, or to dynamically change the context of the keybind is botting.

[Ualaa]

Botting, is unattended play.

Pressing a key, at your keyboard is not unattended play.

If you don't want to use a keystroke up and keystroke down component, then don't.

I again point you to the option of omitting:


Click on the Keymap name (DPS 1, for example). Change, "Execute a Step when the Hotkey is" from "released (Default)" to "Pressed or Released".

[yaki]

Partially unattended, completely unattended? Still botting.

Even having it toggle the bind every time is seriously, seriously pushing the boundaries in the best interpretation.

Anyway, I've said my piece. You've shown that you know it's not right. If you want to bot, that's between you and Blizzard, and if you want to tell others to do so, that's between you and the admins here if they'll allow that kind of thing.

[Ualaa]

Every single last action that occurs is a direct result of your input.
Nothing at all happens ever, while you don't push a key or click something.

That seems to be a very strong indication that there is absolutely no bot action occurring.

By your definition of botting, every single person who uses any software program is a bot, as they all support keymaps, keymapping, hotstrings etc.

It is sad, that people have to throw in the "bot" comments, when that is clearly not the case.

[Ualaa]

Even having it toggle the bind every time is seriously, seriously pushing the boundaries in the best interpretation.

Blizzard has no issues with a hotkey doing one action on keypress one, and a different action on keypress two. They were the ones who implemented something called a castsequence. They even give a bunch of reset conditions for this action, ranging from a time between presses, target switch etc.

IS Boxer achieves the same, by a process called Steps. This is a function which Blizzard has been okay with, for years.

[Pocalypse]

However, they have also specifically NOT given us an option to IWT in a macro.
What you are doing with ISBoxer, is basically adding a /IWT macro line to your action.
I think the fact that blizzard specifically did not give us this option implies they would consider this against their rules.

There is no way to replicate what you are doing with ISBoxer in game, by blizzard's design.

[defactoman]

I can't help but read it as one keypress, two actions (1 (key down) + 1 (key up)). I can't see how its anything other then that. I'm not familiar with any action that we perform thats normally allowed that doesn't meet the criteria one keypress one action. However I know some situations where one keypress = no action which I dont know if they care about.

>a cast sequence is a macro and contained completly in the game under blizards control and allowed

>a spell cast + trinket activated is a macro contained completly in the game and allowed that performs 2 actions.

>an external control that allows one key press to do different actions each one time its pressed is still one keypress one action and considered legal.


I personally would recommend not going with this function.

[Mosg2]

There was/is a bar addon that allowed you to bind downpresses and uppresses and was never stopped.

[defactoman]

What was the mod? There might of been a mod but blizzard turns off functions all the time so might of been disabled at some point.

[Naysayer]

If I hated multiboxers/ing and wanted to add fuel to the fire I would link this post in the general forums, because it is going beyond one keypress= one action.

[Fizzler]

What was the mod? There might of been a mod but blizzard turns off functions all the time so might of been disabled at some point.


button:RegisterForClicks("AnyUp")
button:RegisterForClicks("AnyDown")
button:RegisterForClicks("AnyUp", "AnyDown")

Blizzard allows addons to take advantage of keyup and keydown this is not restricted at this time. Macaroon does this today as does Snowfall keypress

http://www.wowinterface.com/downloads/info15078-SnowfallKeyPress.html
http://www.wowinterface.com/downloads/info10636-Macaroon.html

[Ualaa]

Blizzard has chosen to allow addons to register events for key down and key up: http://www.wowwiki.com/API_Frame_EnableKeyboard

IS Boxer is not doing anything that is not expressly permitted by Blizzard, via their own API.

[genocyde]

That link/API command looks restricted to DIALOG or higher frames. Granted seeing a bar mod capable of doing this seems to suggest otherwise, my concern however isn't the thought of doing '2 actions' with one keypress. I can easily see a key up / key down as 2 separate actions since you can do them independantly and that is the way hardware is traditionally registered with no modification (hence not needing a special keyboard to do such).

It's my choice whether or not to release the key I pressed and when.

My concern is with the combining of the FTL assist macro thats defaulted to the DPS keys and then binding one of those keys to IWT thus having a key that performs and FTL assist (which is fine) and IWT on the same keypress (and i'm talking about having it do both on the same keyDown() not one on keyDown() one on keyUp()).

I'm just curious if there is a way to do this in game or if IS is simply sending a macro to the client followed by a keypress for IWT. Even at the worst case scenario it is a gray area, as I'm thinking this could be done with a /click macro I'm just not familiar enough with them to say.

Anyone that is arguing that one action per key down / key up is botting needs to brush up on some definitions IMO. Botting implies that something is make a decision for the player, something ISboxer clearly isn't capable of out of the box. We were discussing the ToS in regards to the 1 keypress 1 action rule. Not all infractions of this rule are botting, completely different subject.

[VonHenry]

Well, I'm confused. Blizzard is talking out both sides of their mouth. There is zero reason to give us an API that will read key 'depress', and then make this statement.


http://forums.worldofwarcraft.com/thread.html?sid=1&topicId=8765637958&pageNo=1#8

Edit: Not sure why a key depress API would be used for Dialogue or a 'specific' type of action.

That's bunk. What the heck is the "W" key or the "Spacebar" it is one "keypress" with two "actions".
Press to START, Release to STOP. First Law of Motion anyone?? (Yes, I'm being a bit snarky here)
Edit: Yes, Blizzard can do what they want, but I would like to see intentions of those APIs a bit more explicitly stated somewhere.

[genocyde]

I imagine an addon that displays something while holding a key down and stops displaying it when released. (like holding shift while highlighting a piece of gear showing whats currently equipped in that slot and stat comparisons)

That would probably be a very simple and built in use for that API. That is funny that a blue stated one keypress UP & Down to be a 'wow keypress'. Funny how blues seem to contradict each other a lot. There must be zero written rules about these topics at blizzard HQ. It's all a blues 'interpretation' of the ToS just like ours.

[Mosg2]

I get the impression that some people in this thread are approaching it with the mentality that this is wrong and aren't interested in being persuaded.

The functionality exists in game (with this bar mod) for you to do this without the need for a third party program.

[Khatovar]

I get the impression that some people in this thread are approaching it with the mentality that they can do it, so it must be ok and aren't interested in finding out if it's within the ToS, and that does no one here any favors. We do have a blue post right there that says a keypress is the combination of keyup and keydown.

Personally, as a melee team, I'd love to be able to do something like this, but I'm not gonna do it based on who has the more vocal arguement.

I've got a ticket in, how many other people do?

[Pocalypse]

Even with the ability to set up separate commands to key down / key up in game, you CANNOT have a separate commands on one key down / key up, when one of those commands is IWT.

Blizzard did not give us the option to macro this specific ability. You cannot keybind IWT to a keyup command, only to a full key command. Doing so with ISBoxer is doing something you cannot do ingame on a single character.

I think having separate actions on key down / key up is a also not allowed, but looking at those API commands I'm not so sure. Having one of those actions be IWT is definitely not allowed, the way I see it.

[deez]

Key up or key down is irrelevant, it's a two step keybinding. You could just as easily remove half the commas from your melee /click castsequences, or press the button twice as fast, etc.
Is it also illegal for a multi-step keymap to send a key on the first step and a different one on the 2nd?

[Ualaa]

You are not placing IWT in a macro.
You are sending a keybind to the wow game.

A Keymap =/ A Macro.

Looking at the Blizzard API, where they specifically allow addons to register one event on key down, and a different event on key up, tends to suggest this is now ok. At one point, this API did not exist, and I would have said it was not ok at that point in time.

Looking at the API and what it allows, the definition should read: one action per key action. Action 1 is done on they key action (key down) and action 2 is done on the key action (key up). It is two actions, on two key actions.

Blizzard is free to remove this function from the game, but it is currently an allowed function for anyone who can code an addon, or for anyone who can install and use an addon coded this way.

Lax is quick to include any functionality which Blizzard gives us, but IS Boxer sticks to what Blizzard allows; you cannot insert timed delays, perform loops etc.

As always, if you don't want to include key down and key up actions, you don't have to. Just spam twice as quickly, or go with separate keybinds entirely.

[Ualaa]

I cannot see a multi step keymap as being "illegal" with warcraft.

Take for example:

Toon A
/castsequence reset=5 ,Polymorph

Toon B
/castsequence reset=5 Polymorph,

Versus

Keymap
Step 1 - Send Keybinding to Toon A.
Step 2 - Send Keybinding to Toon B.



A multiple step keymap, can send a keybind on each step and nothing more.
Sure, you can include the macro end, within IS Boxer, and have it generate the wow macro for you.
But keybind or wow macro, either way you get only what the wow macro system allows.

My software lets me mash one key.
The game receives two different keybindings, on two key actions.
The same functionality is possible from a player who one-boxes and alternates between pressing each keybinding in turn.
The Keymap does exactly the same thing.












*Edit*

Basically done with this topic, unless someone wants to post on how can they do whatever, with IS Boxer.
If you have an IS Boxer related question, I'd suggest a new thread.
I won't be checking back here.

I couldn't give a shit, whether someone thinks it is right or wrong.
Blizz has given us the functionality to do something in their game.

It is your choice whether you do it or not.

[Naysayer]

Cheaters want to cheat. You know it's 2 actions from one keypress, you're not fooling anyone with your key up/down bullshit. This kind of shit will get multiboxing banned from mmo's in the long run, and deservedly so.

[Fizzler]

I am not even sure why key down/key up is still being debated. It is in the API there are several popular addons that have this ability.

As far as steps in ISBoxer this is a one press one action function.

Anyone who uses Macaroon, the old Trinity, and a slew of other addons that allow you to perform actions on key up and key down are cheaters than? If so I bet you 99.9% of those people are NOT multiboxers.

I know many serious Arena players who use these mods to trigger actions on keydown to speed up reaction time.

[genocyde]

Ya i think Ualaa had the right idea, I'm getting out of this thread as some of the opinions in here are just pure ignorance and it seems that some of the folks are just here to torch and pitchfork at people and aren't even looking at the things presented by each side of the argument.

[Naysayer]

Ya i think Ualaa had the right idea, I'm getting out of this thread as some of the opinions in here are just pure ignorance and it seems that some of the folks are just here to torch and pitchfork at people and aren't even looking at the things presented by each side of the argument.

Even the title says it's automating.

You want to have your F key press perform crusader strike and interact with target. If anyone is ignorant here it's you for trying to fool yourself into thinking this isn't 1press for 2actions when it is. It's you lazy bums who want to automate your characters movement when attacking an enemy that are going to get Innerspace and/or multiboxing banned for the rest of us.

You sound like the posters from the wowglider forums trying to defend their "addons and macros".

[genocyde]

You sound like a typical wow forums bot-blaming nazi. I wanted out of this thread due to comments like that, but it's so hard to just stand by and ignore that kind of mud slinging. I sound like one of posters from wowglider??? Have you even read this thread you miserable troll?

I was in here on page one questioning the legality of having IWT and wow macros on the same key press and I'm not sure my question was ever answered. I offered what I considered usefull insight and my own opinion on the key up / key down question someone else asked and what do you contribute....

You talk about dragging it to the general forums to 'add fuel to the fire', talk about cheaters wanting to cheat and 'our kind of shit' getting multiboxing or software banned. Then you attack me with comments like lazy bum, claiming i want to automate movement, and telling me i sound like a wowglider poster.

1 Keypress = 1 action
Definition - Press:
1.to act upon with steadily applied weight or force.
2.to move by weight or force in a certain direction or into a certain position.

Sounds to me like 1 keypress could be considered the downward motion and another keypress the upward motion. Of course you could argue that the spring under the key applies the force for the upward keypress making it something the user doesn't control.... but I think since it is our option/choice/decision on when and how to release that key, it doesn't fall under automation. This is the topic up for discussion. Feel free to post any opinion, fact or otherwise that is relavent to that discussion or the original topic of the thread.

If all you want to post is flames, I think the general concensus is
"the wow general forums are that way --->"
don't let the door hit you on the way out

[Fat Tire]

You sound like a typical wow forums bot-blaming nazi. I wanted out of this thread due to comments like that, but it's so hard to just stand by and ignore that kind of mud slinging. I sound like one of posters from wowglider??? Have you even read this thread you miserable troll?

I was in here on page one questioning the legality of having IWT and wow macros on the same key press and I'm not sure my question was ever answered. I offered what I considered usefull insight and my own opinion on the key up / key down question someone else asked and what do you contribute....

You talk about dragging it to the general forums to 'add fuel to the fire', talk about cheaters wanting to cheat and 'our kind of shit' getting multiboxing or software banned. Then you attack me with comments like lazy bum, claiming i want to automate movement, and telling me i sound like a wowglider poster.

1 Keypress = 1 action
Definition - Press:
1.to act upon with steadily applied weight or force.
2.to move by weight or force in a certain direction or into a certain position.

Sounds to me like 1 keypress could be considered the downward motion and another keypress the upward motion. Of course you could argue that the spring under the key applies the force for the upward keypress making it something the user doesn't control.... but I think since it is our option/choice/decision on when and how to release that key, it doesn't fall under automation. This is the topic up for discussion. Feel free to post any opinion, fact or otherwise that is relavent to that discussion or the original topic of the thread.

If all you want to post is flames, I think the general concensus is
"the wow general forums are that way --->"
don't let the door hit you on the way out

.....you just proved his point.

[Naysayer]

keystroke
key·stroke (kē′strōk′)
noun
any of the individual strokes made in operating a keyboard, as of a computer terminal.

[genocyde]

Edit: Bah, nevermind I'm back to being done with this thread. I question the legality of whats going on but since nobody wants to have a meaningful discussion about it I'll just continue not using it and exit this flame war.

[Fat Tire]

Edit: Bah, nevermind I'm back to being done with this thread. I question the legality of whats going on but since nobody wants to have a meaningful discussion about it I'll just continue not using it and exit this flame war.

actually no one is flaming that I can see. There is a difference of opinion in the legality of using this method. To have a meaningful discussion I think we would need a Blizzard rep here. Otherwise its just opinions and assholes, everyones got one. :D

[suicidesspyder]

Whew so much hate on this topic. Why doesnt someone just read the whole tos or ask a gm. Once you talk to a gm post what their response is. This way we can stop the nonsense of arguing and saying one person is right and one person is wrong. Go directly to the source and get it str8 from them. Thats my piece on this lol.

[Fat Tire]

Whew so much hate on this topic. Why doesnt someone just read the whole tos or ask a gm. Once you talk to a gm post what their response is. This way we can stop the nonsense of arguing and saying one person is right and one person is wrong. Go directly to the source and get it str8 from them. Thats my piece on this lol.

Well EQ2/SOE just banned boxing as we know it, so its wise not to just take one GM response.

[suicidesspyder]

when did eq2 do that. Does that mean we are next.

[Shodokan]

when did eq2 do that. Does that mean we are next.

With advances in technology and the game changing as much as it is... who is to say blizzard doesn't decide that one person playing 5 characters gives an unfair in game advantage? They do have the right to ban for whatever they want.

The likelyness of bans for boxing are low in my opinion. With more and more boxers coming out of the woodwork (albeit not everyone 5 boxes, but since i posted elsewhere about my plan to 5 box others have had me help them setup 2 box setups like healer/dps for heroics etc) blizzard is getting a higher return on older content from new purchases of games... as well as the extra money per month from all of the extra active accounts and possible services rendered (faction/race change, server change etc).

Blizzard SEEMS to be about the money. Making the game more casual friendly has made a lot of people leave but also brought a lot of new players as well. They do what is best for their game and their wallets.

[Svpernova09]

when did eq2 do that. Does that mean we are next.

The sky is not falling.

[suicidesspyder]

It better not lol. What will i do without running multiple accounts. I cant fathom pugging anymore.

[Fat Tire]

It better not lol. What will i do without running multiple accounts. I cant fathom pugging anymore.

My apologies I didnt mean to muck up this thread.


http://www.dual-boxing.com/showthread.php?t=27225 (http://www.dual-boxing.com/showthread.php?t=27225)

[Khatovar]

Still wondering how many people have actually gone off to ASK instead of sitting here bickering. No one here is going to speak for Blizz, so it's pointless to sit here and flame each other.

[J6mpsikas]

i cant see the problem here, it is allowed to use G15/G11 keyboard for wow, so you can macro multi-keystrokes to its 1 key, so its basicly same as use IVT+action.

[suicidesspyder]

I actually have a question. I put click to move on is there away to change it from right mouse button to left mouse button. I hate having to use the right button when i use the left button to click target. But im just starting to get it figured out.

[Naysayer]

i cant see the problem here, it is allowed to use G15/G11 keyboard for wow, so you can macro multi-keystrokes to its 1 key, so its basicly same as use IVT+action.

Using that function of that keyboard is actually against the ToS.

[Stealthy]

I think this thread has run its course.