FAQ  •  Register  •  Login

Bioware posts clarifications on macros

Moderator: MiRai

<<

Merkwurdigliebe

Posts: 16

Joined: Wed Nov 07, 2012 7:32 am

Post Tue Jun 25, 2013 1:05 pm

Bioware posts clarifications on macros

http://www.swtor.com/community/showthread.php?p=6459160#edit6459160

So a number of people have asked about text macros. A couple of others (even on reddit!) have mentioned 'colour detection to determine which action to take' systems. I even saw a questions about sequence clicking... I even saw claims that we can't detect anything and won't do a thing about this issue.

I'll address all four...

Text Macros
Strictly speaking, text macro's are against the ToS. If its for emotes etc and isn't being used as a way to advise others of an impending attack in a Warzone (inc snow! for example), then we will turn a blind eye to an extent. If you fire off emotes too many times in quick succession of course then you will get evaluated for if you are spamming.

One click 'enter chat, type 'inc snow!', hit enter' text macros designed to warn others is completely against the ToS. You need to make a decision - do I take the time to type 'inc snow' to the ops group, or do I just keep fighting this person... Think of it as an evaluation on if you are using a tool that gives you an unfair advantage over somebody not using that same tool.

Colour detection and evaluated action macros
The very act of determining a colour of a pixel on screen and as a result then using a specific action is one of the easy to understand examples of what we call automation. As soon as you have two things happening based on one key press, then its against the ToS.

Sequence clicking
If you have a system set up so that if you hit the same key 4 times likes so: '1, 1, 1, 1' and instead of just firing off whatever 1 is bound to it fires off '1, 2, 3, 4', then as long as you keep it to 'one key == one other key hit' its in that grey area of not true automation. There is a caveat - you can't have the macro determine a minimum time between clicks to work around the global cool down timing and only fire the next button in sequence if the GCD has expired.

If you instead have a system that when you hit 1, it fires of 1, 2, 3, 4 in quick succession or all at once (i.e. one click == many actions) in order to try and fire something that isn't currently in a cool down state then yes, that is against the ToS. Again, one click must always equal one action and only one action within the game.

Detection of abuse
There are many claims based on guesswork that we can't tell when a person is running automation for systems like field respeccing within seconds. Every time you interact with the server we log either the specific event or an aggregate of similar events firing multiple times. We can (and do!) look through those logs using analytic engines. If you want to know more about the concept, look up 'big data' in google - we strive to make all decisions on making changes to the game based on the data we have, and we have a lot of data.

We also use that data for game forensics - we may not react in a real-time manner for most things, but as people foolish enough to speedhack know, we can and do act based on irrefutable data.

Now, all that said, what are we going to be doing going forwards now that this issue is very much in the limelight?

Expect changes to the ability to field respec in Warzones. We were already working on this as part of some upcoming PvP updates (Bruce detailed some of that this week I believe), and we may bring the field respec changes forward - or we may just keep them where they are so to not impact the game update schedules and instead update our existing Warzone game forensic reporting to include inhumanly fast field respec events. Either way my advise if you are currently macroing within Warzones is to stop.


From what I can tell, it seems anything more than 1-click = 1-action is against the TOS. Now those using ISBoxer are working in a gray area in that 1-click = 1-action on multiple accounts. I always worry about this sort of thing even though I do not multibox (or macro) in PvP. For certain actions (post-combat healing, speeder mounting, attacks with large graphic effects) I will use "round-robin" broadcasting so it looks less likely I am cheating. Has anyone had any experience with key broadcasting vs. "round-robin" in ISBoxer and the TOS when it comes to PvE in SWtoR?
<<

lax

User avatar

Site Admin

Posts: 7301

Joined: Tue Nov 17, 2009 9:32 pm

Post Tue Jun 25, 2013 1:15 pm

Re: Bioware posts clarifications on macros

This actually doesn't specifically address multiboxing. The "one action" is with respect to one instance of the game, not 4, so if you have 4 windows open and you press "1", they're not saying that you can't send 1 to all 4 copies, they are saying that for each individual copy, they don't want you to send "1+2+3+4" at the same time, just "1" (or 1 other button).

In other words, this is okay:
1 -> all

While this is apparently not (as part of a single Step of a Mapped Key, i.e. from a single press of the key):
1 -> self
2 -> self
3 -> self

This applies whether you're using ISBoxer or a programmable keyboard, or placing a popsicle stick over the 1 2 and 3 buttons and pressing on the stick (because it's the same thing).



So this means that you can't put your auto-assist on the same key as your DPS, to make it auto-assist + broadcast. ISBoxer doesn't do this by default for SWTOR, you have to use a manual Assist key. The default 1 through = broadcasting for SWTOR is A-OK according to their statement. You can also use all of ISBoxer's other standard broadcasts, as long as you do not chain multiple keystrokes into the same Step, to the same Target.

So this is okay as part of a single Step:
1 -> is1
2 -> is2
3 -> is3

But this is not okay as part of a single Step:
1 -> self
2 -> self
3 -> self

As per the quote.

Return to Star Wars: The Old Republic

Who is online

Users browsing this forum: No registered users and 0 guests