Better ban most of the gaming keyboards and even the WoW (co)branded mice from Classic while we’re at it now. I can bind /say Hello %t to mouse button 7 without even creating a macro in game, the automation is simply getting out of control. I mean that was a whole 10 key presses I just automated with third party software.
Not necessarily. It could have been removed because, in vanilla, it was sometimes referred to as assist on blizzards end, players and mod authors just nicknamed it focus to distinguish it from the other assists that could exist. Whoever removed it could have also assumed that, because there was no frame for the focus in vanilla, that they may have mistakenly thought that focus didn’t exist in vanilla as well even though it did, it just didn’t have a frame to go with it inherently.
1 Like
LOL where did I argue AGAINST having Focus? Please show me genius. I am actually in favor of adding Focus back in since I used it in many Macros during Vanilla in the way described.
The OP already made a thread on this but it was about Focus and Mutli Boxing. Now they make a thread conveniently ignoring the Mutli Boxing issue. So yeah, this thread is a bit disingenuous but the request is valid. Both can be true.
1 Like
None of the modern code was in vanilla
By your logic none of the modern code can be used because it wasnt in vanilla and none of the vanilla code can be used because it could be exploited.
Sorry every one Classic is cancelled. Shut it down.
1 Like
Yup use some hyperbole there to make a point. Good one.
1 Like
And that script no longer functions in Classic, the /focus API is its replacement. A more restricted version of it at that.
You’ve been pretty adamant that you don’t multi box but want focus.
But you never post why you want it in.
So why do you want it in ?
1 Like
I have posted multiple times why I want it.
I like having a focus from to moniter a target use cc and interupt macros and to use healing macros in pvp.
and then attempted to pass it off as puppetmastering.
You keep using that word, but I do not think it means what you think it means.
A straw man argument is when you make the focus of your argument an imaginary position that you attribute to your opponent.
You can’t say the position doesn’t exist when they are literally calling out the OP for their own expressly stated opinions and intentions.
@OP wants focus to facilitate boxing. This is not in dispute. He started a whole other thread about it.
3 Likes
Same reason people in Vanilla used it so effectively that it was included as a stand-alone frame in 2.0.1+ so people can use it to this day.
1 Like
This in a nutshell. #nochanges has to learn to not have a stick up the nether regions on this category. The lack of an in depth scripting system is a non-negotiable change, one ironically welcomed by many #nochanges proponents.
But because the scripting system has been crippled compared to its Vanilla counterpart, that means the default API needs to be adjusted to allow for new things that were possible via Vanilla scripting, even if the Vanilla API itself didn’t provision for it directly. Because the scripts cannot do that in the Classic version of the game.
That’s not automation.
That still follows the 1 keystroke, 1 action rule Blizzard put in place.
That multi box software sent 1 keystroke to 5 windows but in each of those 5 windows that keystroke only produced 1 action.
OP is not asking for the Vanilla version, they are asking for the today (restricted) version.
Since you’ve asked this a dozen times, and the answer is always no, with an explanation… I’m just going to give you the answer.
No.
For explanation, read every other post. Don’t ask the same follow on tired question that you think entraps that answer, because then I’ll reply with the same tired old answer that proves your entrapment is absurd, and you’ll wait 4 hours and start the cycle all over again.
2 Likes
So why not go over to the add-on thread and ask them how they are getting porting done with this not being in beta.
Surely there are addons that use focus frame.
How exactly are you keeping track of who you claim to be a #nochanger? Is there a chart somewhere?
As yet, no addon has solved the problem because its not solvable with addons.
The focus id has been filtered out at this point and the “Set as focus” menu item has been removed when you right-click on a unit.
And that’s what we’re asking for… the Blizzard implementation of Focus.
No, they won’t. I can point to the literal lines of code that they have to reverse the commit on, in their CMS, to put the slash command and keybind back in, and the focus ID itself needs to be done on the server.
This is such a minimal change that won’t open up any sort of greater automation or issues, because it is already part of the Retail API. They’ve had 13 years to iron out any of what they see as issues, just like they have with target and pet. The request is merely to reinstitute the focus ID because we’re getting the modern API. Their non-Vanilla change put us in a no-mans land between Vanilla and Retail, and they need to add the focus ID to bring us back to a Vanilla-esque implementation of the Retail API, which was their stated goal.
1 Like