-
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/th...958&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.
-
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.
-
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.
-
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?
-
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.
-
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?
-
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.
-
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.
-
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.
-
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.
