Buff Macro problems and Mousebinds in ISBoxer

[jak3676]

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.

[nodoze]

... 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.

[MiRai]

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.

[Fuii]

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.

[MiRai]

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

[Wizeowel]

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.

[Moorea]

> Certainly one in game action for each input (keypush or scrollback detent) is not automation. You can even do 2 actions from a single keystroke as you can legally trigger action on key press and then the second one on key release and it isn't automation...

nope, you shouldn’t do 2 actions in 1 physical key press in combat
that it is « hard to detect » doesn’t mean you should do it

[nodoze]

> Certainly one in game action for each input (keypush or scrollback detent) is not automation. You can even do 2 actions from a single keystroke as you can legally trigger action on key press and then the second one on key release and it isn't automation...

nope, you shouldn’t do 2 actions in 1 physical key press in combat
that it is « hard to detect » doesn’t mean you should do it

That was already well pointed out above on 7/27 with the quote of the applicable blue post.

I went ahead just now and changed my post above to denote that so we don't repeat things already said/corrected.

Doesn't change the overall points of my replies that "AI" isn't necessarily the same as "Automation" and that, while the rules are somewhat subjective, it matters whether you are in combat or not...

[Moorea]

as long as it starts to sink in that using isboxer to cast 2 combat spells in 1 key or use time delay isn't right, we're all good