Multicyclopedia Request: Interact With Target / Click To Move

[Tim]

Hey Ualaa,

I've seen a lot of activity in the forums and website lately about how to use IWT/CTM. The amount of people searching from google and finding the site is pretty huge, something like 5,000 pageviews/day for IWT stuff just in itself.

Since you're a multicyclopedia, any chance you could do an awesome write up, maybe even include a couple pictures for where the areas are at in the UI, maybe [code] brackets for macros to turn it on/off, and then I can post it up as a guide as well as make an article for the front page?

Cheers!

[Ualaa]

Pretty rough draft here.
But it is something.

Also can edit out my software stuff, and keep it very basic if you prefer.

Or can leave it in, to give an idea of what you can accomplish; most of it could be adapted to work with any of the stronger software options out there.




Near the start of Wrath of the Lich King, Blizzard introduced a couple of features aimed at making Warcraft easier for people with disabilities. These were Interact With Target and Interact With Mouseover. The first of these combines with an existing feature called Click to Move, to make melee boxing in particular much easier. Every composition can benefit from this, with easier interaction with friendly NPC's too.

Click to Move can be set in Interface Options - Mouse Options.
Check the box or uncheck the box.
You can also set it, via macro:

/Console AutoInteract 1
/Console AutoInteract 0

1 = On
0 = Off

Interact With Target, is set in Keybinds - Targeting Functions.
This is a keybind only, and cannot be put into a macro.



The basic functionality is to target an NPC.
Have the slaves assist the active character.
Press your IWT keybind, while Click to Move is enabled.

Your slaves (and main, if they have CTM enabled) will move towards the target.

If the target is friendly, they will open the menu.
For options such as Buy/Sell, Set your Hearthstone, or Open the FlightPath window.
This combines very well with the slave copying the main, via the Jamba Addon.
You can use this for quest selection and turn ins too.

If the target is hostile, they will move towards where it was when you clicked your IWT keybind.
And once they get there, start auto attacking.
If the target moves, press the keybind again and the toons will move to the new position.
For PvE play, you are best off pressing this once and not spamming.
For PvP play, you have to spam to keep up with a moving target, which results in circling the target rapidly.
However, when the target dies, your toons will frequently run off in whatever direction they were previously moving; a quick /Follow (or giving them a new IWT Target) can have your toons regroup fairly easily.




I have a mapped key, set to two steps.
Meaning it does something on the first activation and something different on the second.
I have it set to execute a step on both press and release.

On press, it sends IWT to all of my toons.
And on release, it sends Down Arrow to all of my toons.

This lets me have my toons auto face my target for recovery after fear.
Or if they decide to strafe through my toons.
A quick tap is all I need for facing.
But holding the key (not releasing) initiates the following (or charging to the target) to close the distance.
This would be easy to set up with two keys as well, or two successive presses of the same key if you didn't want press and release functionality.




I've also got what is called an Action Target Group, which is a preconfigured group of toons who will receive an action, in this case I've named the ATG Melee IWT. I have twenty or so ATG's, for various functions across my teams.

I've created a mapped key (Melee IWT), which sends my IWT keybind to the Current Window.

I then take my DPS Keys, and modify them to be two Steps.
The first step has the slaves assist the main character.
It also runs the Melee IWT mapped key, but only for members of my Melee ATG (Action Target Group).
The second step sends the hotkey which activated the mapped key (1, 2, 3, etc) to all windows.

Finally, I have a toggle key.
This key enables and disables my Melee IWT mapped key.
When the key is enabled, my DPS automatically sends IWT to my melee toons (members of the Melee IWT ATG).
But I can disable the Melee IWT mapped key, which means it cannot execute and no one receives IWT.

In play, I can press my DPS 1, DPS 2 or DPS 3 mapped keys.
If my toggle is on, this has melee toons on my teams, IWT in addition to whatever is on their DPS keys.
If my toggle is off, there is no IWT.

I also have an IWT Mapped key, which sends IWT to all windows. I use this in PvE for quest npc's or occasionally for looting (target a corpse, and spam a DPS key, which has the slaves acquire that corpse and interact with it).

You could duplicate this functionality, by having two IWT keybinds.
Have one set for only your melee characters.
Have another for all of your characters.
Press the melee key only, and the melee with IWT but the casters (if your team was a mixed team) would not.

[Tim]

Yea keep it software neutral (I prefer all the guides to be software neutral actually).

Super tired now but will be reading tomorrow I'm sure!

And thanks!

Edit: Can you maybe put a screenshot of where in the WoW config the options are at?

PS: Somebody has a birthday coming up, right?

[Tybudd]

This mapping technique of the IWT keybind is intriguing, do you have an actual guide on mapping keys?

[Tim]

The keys are part of WoWs default UI actually. Just go into the options, enable the keybind, as well as enable the mouse option.

If somebody would, could you please post 2 screenshots of those areas?

[Tybudd]

Originally Posted by Tim

The keys are part of WoWs default UI actually. Just go into the options, enable the keybind, as well as enable the mouse option.

If somebody would, could you please post 2 screenshots of those areas?

That part i got, for example my IWT is bound to my

\

button, thats a basic bind, maybe I'm getting confused with the "keymapping" term, they aren't 1 in the same are they?

[Ualaa]

CTM = Click to Move
IWT = Interact With Target

CTM = Option in Interface - Mouse Options, which is enabled or disabled via the check box, or via the /console AutoInteract script (1 = on; 2 = off).

IWT = A keybind - in the Targeting Functions section. Cannot be macro'd.

[Tybudd]

What about the keymapping option, to set 1 funtion on down press, and release of the button? HOw is that being done?

[Tim]

Originally Posted by Tybudd

What about the keymapping option, to set 1 funtion on down press, and release of the button? HOw is that being done?

That is something I would stay away from as this is very gray to what is considered botting. I personally consider that botting as it doesn't crystal clearly follow the 1 keystroke = 1 action rule.

[Ualaa]

The up/down is done by the IS Boxer addon, which uses the World of Warcraft Keyboard API. IE, this is an action which takes advantage of something Blizzard intentionally put into the game and could not work if Blizzard choose to remove that feature. To my knowledge there are two other addons that take advantage of this feature: Macaroon and Snowfall.

Blizzard choose to include that functionality in their API code for addons to use. Some software options include an addon as part of the software and others do not. Without an addon to interpret this for Warcraft, you cannot use this functionality.



The thread with one keystroke = 1 action has been misquoted hundreds of times.

The GM was rather specific on what constitutes botting; specifically if every action is a result of an input you do then and there, you're fine. For example having a single key output both W for forward movement and Q for strafing left, for as long as the key is held is completely fine, since the action (forward + strafe) is a direct result of your input.

But if you can push (or release) a key or click the mouse now, have something occur now and then without any further input from the user have the software do something different at a later time, and then another action a few seconds after that, again without any further input from the user -- that is more than one action from a single input.



I'll find the one keystroke = 1 action rule, and link it to be crystal clear.