Trade chat macro Bannable or not?

"

syrioforel wrote:

"

reboticon wrote:

my /oos macro works fine without sleep, actually.

But etup doesn't.

"

Alhoon wrote:

Second is by detecting injected keypresses. This is a bit more technical explanation, so bear with me. Autohotkey and similar software sending keypresses have KBDLLHOOKSTRUCT LLKHF_INJECTED flag set as 1, since they are injected keypresses (or in case of mouse events, MSLLHOOKSTRUCT LLMHF_INJECTED 1). Identifying macros becomes a case of detecting this flag when reading input stream and depending on what dev wants to do with it, either ignoring all events with that flag (quite radical approach and would probably lead to problems) or more likely flagging such events as injected events as far as internal logging goes, and maybe implementing harsher parsing for those events.

As far as cat and mouse game for this one goes, I know there is a way to bypass LL*HF_INJECTED flag getting into input stream at all, but that requires using hex editor on Windows Kernel level component, which is not a simple task for anyone, and downright impossible for vast majority of players.

If anyone's interested in this topic, here's a bit more discussion, it's fairly large thread but a good one: http://www.autohotkey.com/board/topic/785-a-program-that-defeats-autohotkey/

"

Muji_k wrote:

currently i have bind the permited oos macro, that only gives one command each time a key is pressed, to my main main attack key so every time i attack i try to send the command to the server, i know that the command can only be repeated once each 10s but as i can't make the loop macro, this was the only way i could found to repeat the command each 10s without having to press an extra key each 10s too or without becoming illegal.....

"

unsane wrote:

"

Muji_k wrote:

currently i have bind the permited oos macro, that only gives one command each time a key is pressed, to my main main attack key so every time i attack i try to send the command to the server, i know that the command can only be repeated once each 10s but as i can't make the loop macro, this was the only way i could found to repeat the command each 10s without having to press an extra key each 10s too or without becoming illegal.....

That's an ingenious way to get around the rules. Ironically, a 10s timer /oos (which isn't allowed), is far better for them than your above solution (which is allowed, i think).

"

alexanderthegreat wrote:

2) Unfair advantage over someone else.