Close
Page 2 of 2 FirstFirst 1 2
Showing results 11 to 16 of 16
  1. #11

    Default

    The "per keystroke" thing is a rule for external programs that WoW cannot internally enforce.
    Can you elaborate? I'm not following you.

    We're talking about an addon, which has a security system that WoW can enforce. See https://wow.gamepedia.com/Secure_Execution_and_Tainting
    I fully understand that the addon operates within the authorized API that Blizz controls and enforces - if there's any concern there, its up to Blizzard to enforce within their API. I don't see anything wrong/risky with anyone using the addon, or with people here recommending it.

    What does seem odd to me is that the addon is doing something that Blizzard specifically said they were trying to prohibit addons from doing - intelligently deciding to cast the buff or not to cast the buff based some logic within the addon. From the link you provided above, "
    2006-10-06 00:00 | sloukenJust to clarify, AddOns and macros will still be able to cast spells (with user interaction of course), they just won't be able to use logic to intelligently pick spells or targets.
    Sorry - not trying to stir up any drama here, where I really don't think there is any. I think I agree with you. I'm just trying to understand.
    Last edited by jak3676 : 07-27-2020 at 03:13 PM Reason: Merged

  2. #12

    Default

    Quote Originally Posted by jak3676 View Post
    ... What does seem odd to me is that the addon is doing something that Blizzard specifically said they were trying to prohibit addons from doing - intelligently deciding to cast the buff or not to cast the buff based some logic within the addon. From the link you provided above, "

    Sorry - not trying to stir up any drama here, where I really don't think there is any. I'm just trying to understand.
    I think the difference is, at least in part, convenience vs combat.

    If you set SmartBuff to try to buff in combat logic goes out the window and it casts over and over.

  3. #13
    Multiboxologist MiRai's Avatar
    Join Date
    Apr 2009
    Location
    Winter Is Coming
    Posts
    6783

    Default

    Quote Originally Posted by jak3676 View Post
    Can you elaborate? I'm not following you.

    I fully understand that the addon operates within the authorized API that Blizz controls and enforces - if there's any concern there, its up to Blizzard to enforce within their API. I don't see anything wrong/risky with anyone using the addon, or with people here recommending it.

    What does seem odd to me is that the addon is doing something that Blizzard specifically said they were trying to prohibit addons from doing - intelligently deciding to cast the buff or not to cast the buff based some logic within the addon. From the link you provided above, "

    Sorry - not trying to stir up any drama here, where I really don't think there is any. I'm just trying to understand.
    My response isn't aimed directly at you, but this seems to need repeating from time to time.


    1. Add-ons cannot do anything that Blizzard doesn't allow.
    2. If an add-on can do it, then Blizzard allows it, since the Lua sandbox is 100% under Blizzard's control.
    3. Never, in the history of add-ons existing in World of Warcraft, has any player been banned for using an add-on.
    4. Furthermore, if Blizzard doesn't like the way an add-on is performing or being used, then Blizzard will simply restrict the code that the add-on uses.
    Do not send me a PM if what you want to talk about isn't absolutely private.
    Ask your questions on the forum where others can also benefit from the information.

    Author of the almost unknown and heavily neglected blog: Multiboxology

  4. #14

    Default

    Quote Originally Posted by MiRai View Post
    Furthermore, if Blizzard doesn't like the way an add-on is performing or being used, then Blizzard will simply restrict the code that the add-on uses.
    And that part came true couple of times in Classics history already; like changing the log range of character actions/abilities to cripple various spy addons.

  5. #15
    Multiboxologist MiRai's Avatar
    Join Date
    Apr 2009
    Location
    Winter Is Coming
    Posts
    6783

    Default

    Quote Originally Posted by Fuii View Post
    And that part came true couple of times in Classics history already; like changing the log range of character actions/abilities to cripple various spy addons.
    The earliest instance I can remember such a thing happening was back in WotLK, when Blizzard broke the AVR add-on, which was used to draw on the game world to assist with raid positioning.

    Article w/ Blue Post: https://www.engadget.com/2010-05-20-...tch-3-3-5.html
    Example: https://www.youtube.com/watch?v=fimaiHFp3aM
    Do not send me a PM if what you want to talk about isn't absolutely private.
    Ask your questions on the forum where others can also benefit from the information.

    Author of the almost unknown and heavily neglected blog: Multiboxology

  6. #16

    Default

    Quote Originally Posted by nodoze View Post
    I think the difference is, at least in part, convenience vs combat.
    Totally this. Combat in Wow is really the big on/off switch for automisation.

    They didn't want to break auto-buffing addons, because was a serious quality-of-life thing especially for paladins back in vanilla days. But they did want to break healbot and similar addons which chose target and most efficient spell rank for you.

    Incidentally, for the first few months of Classic Button:SetEnabled was unprotected during combat, so you could automate things by enabling/disabling a button that contained a macro.

Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •