So I recently noticed that the mob Prat has the functionality of adding a new command for macros, called /in. What it does is simple, it will execute the command in a number of seconds, that you specify. So for example :

/cast Blood Lust
/in 4 /s BLOOD LUST UP, GOGOGOGO!

This macro will cast blood lust, wait 4 seconds, and then say "BLOOD LUST UP, GOGOGOGO!"

Harmless yes, but as a multi-boxer, I have been told to stay away from useing time delays, because abused correctly, it can be used to possibly be automation.





My question for blizzard is simple. Is this /in command ok? I don't want to use it and get 4 accounts banned....

You should ask on the macros forum

They know all about this sort of thing

---

Q u o t e:
So I recently noticed that the mob Prat has the functionality of adding a new command for macros, called /in. What it does is simple, it will execute the command in a number of seconds, that you specify. So for example :

/cast Blood Lust
/in 4 /s BLOOD LUST UP, GOGOGOGO!

This macro will cast blood lust, wait 4 seconds, and then say "BLOOD LUST UP, GOGOGOGO!"

Harmless yes, but as a multi-boxer, I have been told to stay away from useing time delays, because abused correctly, it can be used to possibly be automation.

My question for blizzard is simple. Is this /in command ok? I don't want to use it and get 4 accounts banned....

---

I'm quite positive it will lead to a ban. The G15 is the same way. While it has the ability to create a 'pause' in a macro you are not permitted to use the feature.

---

Q u o t e:
I'm quite positive it will lead to a ban. The G15 is the same way. While it has the ability to create a 'pause' in a macro you are not permitted to use the feature.

---

You're incorrect. The /in function can't be used to do anything that requires a hardware event, and therefore cannot be used for botting. You're fine to use /in for anything that doesn't require a hardware event, such as sending a line to chat. The G15 time delay does send a hardware event, and that's why it's an issue that it's on a timer.

---

Q u o t e:



I'm quite positive it will lead to a ban. The G15 is the same way. While it has the ability to create a 'pause' in a macro you are not permitted to use the feature.

---

Aye, thats why I asked. But, I thought I heard some where along the lines that if it was something a mod could do, then it was legit in blizzard's eyes. Most likely wrong, but I want to make sure first. I'd love to hear from a blizzard poster on this.

On a side note, I'll be letting my friends back @ dual-boxing.com know the verdict, because if it is allowed, this could be very useful.

---

Q u o t e:
You're incorrect. The /in function can't be used to do anything that requires a hardware event, and therefore cannot be used for botting. You're fine to use /in for anything that doesn't require a hardware event, such as sending a line to chat. The G15 time delay does send a hardware event, and that's why it's an issue that it's on a timer.

---

I don't quite understand this, but that's probably because I don't know much about coding. I would assume there would be no difference between "/say Gogogo!" and "/cast Steady Shot", but apparently one is a 'hardware' event? How does that work?

---

Q u o t e:


You're incorrect. The /in function can't be used to do anything that requires a hardware event, and therefore cannot be used for botting. You're fine to use /in for anything that doesn't require a hardware event, such as sending a line to chat. The G15 time delay does send a hardware event, and that's why it's an issue that it's on a timer.

---

Right, I see the difference, but what throws this into the grey area for me is a program called Auto Hot Key, which some multi-boxers use to software box. It's basically a program that you must enter your own code to do the commands for you. I don't really know anything about it, but long story short, I've heard warnings from other to stay away from it, because it can be used to send delays, and I believe also key presses. It made me wonder if the /in could do the same.

Sorry for the confusion, just making sure I don't do anything against the ToS :)

---

Q u o t e:


I don't quite understand this, but that's probably because I don't know much about coding. I would assume there would be no difference between "/say Gogogo!" and "/cast Steady Shot", but apparently one is a 'hardware' event? How does that work?

---

They are both events in game. He means Hardware event, as in a key press, or a button click.

---

Q u o t e:


I don't quite understand this, but that's probably because I don't know much about coding. I would assume there would be no difference between "/say Gogogo!" and "/cast Steady Shot", but apparently one is a 'hardware' event? How does that work?

---

I think the long and short of it is that if it can be written using the macro code, then it's probably fine.

As Evilpixie has said, /in won't work with casting spells, but it will work with chat functions. Therefore, it's probably fine

---

Q u o t e:


You're incorrect. The /in function can't be used to do anything that requires a hardware event, and therefore cannot be used for botting. You're fine to use /in for anything that doesn't require a hardware event, such as sending a line to chat. The G15 time delay does send a hardware event, and that's why it's an issue that it's on a timer.

---

Interesting. I was not aware of that.

---

Q u o t e:
Right, I see the difference, but what throws this into the grey area for me is a program called Auto Hot Key, which some multi-boxers use to software box. It's basically a program that you must enter your own code to do the commands for you. I don't really know anything about it, but long story short, I've heard warnings from other to stay away from it, because it can be used to send delays, and I believe also key presses. It made me wonder if the /in could do the same.

Sorry for the confusion, just making sure I don't do anything against the ToS :)

---

I believe Auto Hot Key is perfectly fine as long as you avoid the delays - same as with the G15 - but I'm not 100% sure on that. The /in can't send hardware events, since it's part of an addon that has to go by Blizzard's rules for addons, which don't allow for the ability for an addon to send a hardware event.

EDIT: a "hardware event" is a keypress, or mouse click or movement, or perhaps some other similar event such as a joystick (I've heard of some people getting some types of gamepads working with WoW).

---

Q u o t e:
I believe Auto Hot Key is perfectly fine as long as you avoid the delays - same as with the G15 - but I'm not 100% sure on that. The /in can't send hardware events, since it's part of an addon that has to go by Blizzard's rules for addons, which don't allow for the ability for an addon to send a hardware event.

---

Okay, I think I understand now. When I saw the term 'hardware event', I assumed it meant computer hardware, thus my confusion over the difference between /say and /cast. Am I correct in the presumption that 'hardware events' are a separate class of scripting, then?

---

Q u o t e:


I believe Auto Hot Key is perfectly fine as long as you avoid the delays - same as with the G15 - but I'm not 100% sure on that. The /in can't send hardware events, since it's part of an addon that has to go by Blizzard's rules for addons, which don't allow for the ability for an addon to send a hardware event.

---

From what I have heard, you are correct, but in the same way as you are supposed to be wary of key delay with auto hot key, I thought you might need to be wary of it with mods.

---

Q u o t e:


I don't quite understand this, but that's probably because I don't know much about coding. I would assume there would be no difference between "/say Gogogo!" and "/cast Steady Shot", but apparently one is a 'hardware' event? How does that work?

---

Chat and cosmetic UI changes can be completely automated, but gameplay-affecting actions like spellcasting, movement, and so on require hardware events like mouse clicks or keypresses to initiate. One such action "consumes" one hardware event. There are exceptions, of course, but that's the basic idea. The upshot is that addons and scrpts and such cannot artificially create such hardware events, but specialized hardware like the G15, Nostromo keypad, and such can. That doesn't make owning or even using such devices a problem, unless you use their capabilities to generate automated hardware events.

I just gave the /in 4 /cast healing wave a try, and it doesn't work. Gives me this error message.

"Error, /in cannot call secure command: /cast"

So looks like you can't do a delayed cast with it.


I'll have to wiki what commands are secure and unsecured, to see if there is still any use for this :(

---

Q u o t e:
Okay, I think I understand now. When I saw the term 'hardware event', I assumed it meant computer hardware, thus my confusion over the difference between /say and /cast. Am I correct in the presumption that 'hardware events' are a separate class of scripting, then?

---

Your assumption was correct. See my edit above.

Just FYI, I'd edit out the bit about the shaman exploit (especially the macro). While it is relatively common knowledge, the GMs don't like seeing it publicized further.

Well as long as this can't be used to move or cast in some way so that you can't push the macro, and have it move 4 minutes later, to keep you from going AFK in a BG.

---

Q u o t e:


No, time delays inserted into a Macro are not okay - this is largely part of the reason why certain macro functions of the G15 can cause account actions, as well as the macro functions attached to some of the newer gaming mice.

That said, our macro 'language' does not allow for delays on 'hardware' events. Even so, while communication based delays shouldn't be as much of an issue, I'd avoid using them anyway.

---

Ok, so I should avoid using the /in command? Will do :)

---

Q u o t e:
Just FYI, I'd edit out the bit about the shaman exploit (especially the macro). While it is relatively common knowledge, the GMs don't like seeing it publicized further.

---

I don't think they will mind, they have fixed that exploit now anyway, doesn't work any more.