Guild Wars 2

Add to that: the software can’t make decisions in place of the player.

Well, that was my main point as I couldn’t see that point in the policy. But if you are sure, I think I will have to accept it.

EDIT: Interestingly I found ‘software that intercepts or otherwise collects data from or through the Game;’ which might or might not apply to parsing data from screenshots in principle

EDIT II: Well, it seems you are probably right. If they were completely allowed you could just program a regular bot which just would perform the next action on the next keypress which, in turn, could be generated by a stone (or any other sufficiently heavy item) on the respective key on the keyboard.

I think the active window can be even detected without using the Windows API (as I said, I already think it is borderline to think of using that as not allowed as it is e.g. required to check the active window even for deciding whether to apply a macro based on whether e.g. Guild Wars 2 or Google Chrome is running) by just listening to mouse-clicks and alt-tab key inputs and “calculating” the active window based on that. Would that change your opinion for the first part?

Sorry, that is 100% untrue. I haven’t even asked whether such a thing would be allowed since I know it isn’t. I also have no such program but actually maybe intend to program something like that if it was allowed.

Um, it’s a completely different thing to be detectable and to be allowed.

Also, I don’t see how I could go afk with the macro I mentioned – at least not more as with the macro explicitly stated as allowed (perform an action in a background window – where you would not read any GM messages).

Anyway, such macros could – in principle – be detected rather easily if not done in hardware, I think.

That’s for one key – first action A, then B, then … macros

I know, but there is “You may not program a single key to perform multiple functions.” in there. On the one hand, this could mean that the things I mentioned are forbidden as one action is performed from multiple possible actions. On the other hand, the examples which follow only talk about performing multiple actions for one keystroke at the same time.

Well, I read it as that 1 key should not perform multiple actions at the same time, but nothing about whether it has to perform the same action whenever pressed.

How is the macro going to figure out which window is currently active?

There are some Win32-Calls for that. I don’t think this is regarded as interacting with Guild Wars 2 because it just interacts with the Windows API

That is doing two things so an automatic no.

No, I mean when you press Q the first time, it acts like “4” in the first window, when you press Q the second time, it acts like “5” in the second window.

if ANet is feeling lenient, I would guess context-dependent actions on activation wouldn’t be against the spirit of the rules

Well, the thing is, while I don’t think it allows ‘better’ play, it allows more ‘braindead’ play (maybe, as I haven’t tried it out I don’t know) which might or might not be considered as rule violation.

Hi everyone, I have the following question:
I understand that a macro may only remap single keys to single keys.
However, this requirement still does allow several kinds of macros which might be considered as abusing.

Thus, I want to ask whether the macros are “intelligent”, i.e. depend on some external factors, are allowed, i.e.:

• Pressing ‘Q’ does something different depending on which window is currently active, e.g. uses Skill 4 when one window is active but Skill 5 when the other window is active
• Pressing ‘Q’ does something different depending on how many times Q has been pressed in the last 10 seconds, e.g. a ‘combo’ can be done by just repeatedly pressing the same key
• Pressing ‘Q’ does something different depending on whether the health percentage, captured by parsing the screen content, is below or above a certain value, e.g. casting an attack skill when the health is high or a heal skill when the health is low
• Pressing ‘Q’ performs an action in a different window depending on some condition (e.g. one defined above), e.g. first activates Skill 4 in the first window, then Skill 5 in the second window