http://www.wowwiki.com/World_of_Warcraft_API
Here, read through that and why such things can be restricted via PROTECTED and NOCOMBAT classes.
Decursive has, or had, an option to auto-heal you, but only while out of combat.
http://www.wowwiki.com/World_of_Warcraft_APII'm still not sure what you are saying. I'm not taking about anything being automated by the API. I'm talking about using the API to create automation. For example if you allow your API to see player health which has plenty of legitimate uses, then allow your scripting language to perform conditionals/iteratives/comparisons which again has legitimate uses then allow for execution of commands, none of these three in themselves are automation or arguably malicious.
But when you put the three together, then you start running into problems. Give the user the three controls above in FF14 and you can make a White Mage play itself other than executing the macro similar to what HealBot does in WoW.
This is the kind of risk you run by opening your interface up. The more information and controls you expose the higher the risk that people will just further automate tasks in the game to the point that they are just running complex scripts rather than playing the game. Sure you can just argue that good people won't use them but that really doesn't solve the problem.
Here, read through that and why such things can be restricted via PROTECTED and NOCOMBAT classes.
Decursive has, or had, an option to auto-heal you, but only while out of combat.
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.