What is GGG's stance on macros?
" I guess it is better to give examples to clarify the confusion. By automation I mean; Consider I developed a program that can read the text above the health globe with OCR (Optical character recognition). If this said program sends alt+f4 command when health drops under 100. This is automatization. Player didn't initialized a command everything happend automatically. We all can agree this is against ToS. By macro I mean; Binding in game commands "/oos", "/itemlevel" etc. to buttons. Which needs to be initialized by the player to happen. There were lots of threads regarding this. People shared their macros on the forum with each other. GGG didn't made a comment while these are publicly happening. So I assume that if the macro doesn't exploit the game mechanics, GGG is fine with it. No longer a forum dweller, please use PM for contact purposes. Последняя редакция: ignarsoll#5178. Время: 9 июл. 2013 г., 04:19:29
|
|
|
A macro is automation, in the most pedantic sense.
I agree with you that I would not expect simple macros to be punishable. |
|
|
I admit i also use a /itemlevel /oos and /remaining macro.
/oos because i Use Multistrike + Cyclone and the amount of desyncs with it are HORRIBLE. I have to run it after practically every cyclone. The other two are just convenience things which don't harm anyone. I'm very against botting and would never automate skill usage or incorporate something in the sense of OCR. Even making an Alt + F4 macro is overdoing it. Heck if people use Alt+F4 in hardcore leagues you're not really hardcore, you're a wuss posing to be a Hardcore player. In certain circumstances (Massive desync) I can understand. Doing it because you are losing life just makes you a poser. If GGG would release an official statement that this is against the rules I would turn it off without making a big deal about it. I Would want them to fix desync considerably though as compensation as the /oos macro has saved my butt more then once. Lead or Follow but get out of my way. -Thomas Paine
|
|
" What? Where did I say this? I swear that people on the internet seem to always make out reading to be like rocket science or something. IGN: ThrobbinRobin
|
|
|
if i macro all flasks as one keystroke = illegal? G700 here.
it would be a nice multi purge, lol Последняя редакция: NomadFX#0730. Время: 9 июл. 2013 г., 11:43:58
|
|
|
Sorry to "hijack" your thread but i posted a question about this on general discussion and got some GGG responses:
http://www.pathofexile.com/forum/view-thread/457851 Hope this clears up some things. Regards. [2.2] The Vampire - Tanky 2H Axe Slayer Duelist - /view-thread/1611662
|
|
" I don't consider this hijacking as this is just referring me to a post made by GGG staff. Thanks for the info =). IGN: ThrobbinRobin
|
|
|
When they fix desync they can then ban /oos macro. Until then, oos on.
|
|
|
A dev was talking about it in global once.
Macros that do not give you an UNFAIR advantage against enemies IN ANY WAY but make tasks such as /oos /itemlevel Less annoying... are allowed as would be any more along these lines. /oos simply restores a user from disadvantage and so is not unfair. Unfair advantages will/may include: MF gear swapping (will) Logging out/Alt F4 Macros (may) Skill sequence macros such as enduring cry enduring cry, curse, discharge instead of clicking 4 buttons yourself (will) Auto potion macros (such as when life < 50% use flask) (will) etc etc. The only one im not sure about as in gives advantage (even though it kinda does in some ways and doesnt in others is logging out). Why am i not sure about logging out? Well, it does not make your fight against the enemy any easier it just prevents death easier. So it could be considered not an advantage against the enemy but it is an advantage to saving your char or saving exp loss. |
|
"+1. Personally, since they are technically against the ToS, I think all macros are technically banable, although the choice to ban accounts for their use is and should be totally up to GGG discretion. In terms of what GGG's discretion should look like, I think you've pretty much nailed it; no action on /oos and /itemlevel, swings of the banhammer for that last grouping. I think auto-logout macro should result in a ban eventually, but should be treated with slaps-on-the-wrist first, no bans for first offense. When Stephen Colbert was killed by HYDRA's Project Insight in 2014, the comedy world lost a hero. Since his life model decoy isn't up to the task, please do not mistake my performance as political discussion. I'm just doing what Steve would have wanted.
|
|
