A macro script has been blocked from an action only available to the Blizzard UI?

There was a macro in a youtube video from October last year that had hunter macros for classic but when I try to run it I get this error. They are listed as Raziya The Ravager’s Amazing Hunter Macros by this person at at 21:38 in this youtube vid

This is the macro

/script if GetUnitName(“target”)==nil then TargetNearestEnemy() end
/run if CheckInteractDistance(“target”, 3) and (not PlayerFrame.inCombat) then AttackTarget() elseif not isAutoRepeatAction(3) then CastSpellByName(“Auto Shot”) end

Unsure what’s wrong so yeah figured i’d ask here

in another thread, someone mentioned that scripts were blocked in classic.

1 Like

Classic runs on the legion engine and uses most of the legion API rules. As far as I recall, they blocked macros from being able to check distance and then make choices for the player based on the information.

Basically, Blizzard removed all logic from macros like that. Only the player can make the “If=>Then” decisions. There are some exceptions though, but they mostly don’t have to do with combat.

1 Like

Damn :frowning: alot of these macros have them in it and without them it takes ages to tell a pet to do anything and if I right click my character melee attacks as a hunter while i’m miles away from the enemy. Sucks having pet following a mob that’s running away and agroing while i’m trying to move my mouse to a tiny button :frowning:

You can just keybind /petfollow and hit that increase manually clicking. Granted it feels like hunters has a truck load of keybinds they need.

Maybe try playing the game yourself rather thasn relying on automation?

10 Likes

You can make more keybinds than the 12 it gives you by default. That way you can have melee or pet attack be a button you press on your keyboard instead of having to click on something since clicking is sometimes wonky when things pile on top of each other or are moving quickly, etc.

And for the shoot problem specifically, under the general section of your spell book, the top tab, that “Auto Shoot” button you referenced in your macro is hiding in there

Those are old macros from vanilla/private servers. Updated versions can be found here:

https://classicwow.live/guides/893/hunter-macros-tips

As a lock every single button on my pet action bar is keybound and i do all the control manually.

Also I have some manual dexterity issues so can’t use too many keybinds so I end up having to mouse to and click the auto shoot button if i’m out of mana and not shooting anymore which takes a very long time

How about one of those fancy mice with like 20 extra buttons on them? They’re made for games like wow so you can keybinds to that if it would help

Had a razer naga epic a few years ago and the side buttons required so much force to press that any time a button on the side was pressed the mouse moved a few inches on the screen :frowning:

Did you have it on a mouse pad? Maybe a higher friction one would help or maybe try lowering the mouse sensitivity.

Having boatloads of abilities (and therefore keybinds) is just a part of classic for pretty much every class… I’m actually not sure if any of them can get away with just 2 bars of keybinds (24). :frowning:

Always use a razer mousepad. Atm I have a Deathadder.

Classic does not use the Legion engine. The BlizzCon demo used Legion. Classic uses BfA.

Your point still stands, they are usong the modern API

No, as far as I know, the engine is still the legion engine. When you develop a game using an engine, you pick a version and stick with it usually. For example, if you’re using the Unreal Engine, your team might pick 4.21 and by the time you’re done, UE4 might be on 4.27. However, your project will remain on 4.21. You don’t constantly upgrade your game to new versions throughout the development because that leads to a lot of refactoring and breaks.

It’s not, when the alpha was available for download. The people that data mine verified the switch to 8.x

If you have the energy you could sift through the old forums and find the theads about it.

Yeah I looked around and from what people are gathering, they put in the 8.1 API, but the actual client is somewhere between 7.3.5 and 8.0.1. The fact that classic doesn’t have DX12 or multithreading is definitely the big indicator that it’s not completely BfA though.

That could explain a lot of the bugs and issues that have been arising.

DX12 was asked and answered in an interview. Can’t remember why they don’t want it but it was purposely omitted. Haven’t seen anything commenting on multithreading

Edit: DX12 makes a significant increase in system requirements, that’s what it was