Focus was in Vanilla - Please Fix the API

That is a function. The OP and their partner are talking about /script usage.

Ah yes Fakespeare

1 Like
SlashCmdList["ASSIST"] = function(msg)
	if ( GetSlashCmdTarget(msg) ) then
		AssistByName(GetSlashCmdTarget(msg));
	else
		AssistUnit("target");
	end
end

From 1.12 ChatFrame.lua

Blazilz you realize you can be reported for harassment? I suggest you stop.

Actually we’re not, and “that function” is something you call from /script…

The request is for them to reinstate the focus unit ID. Not reinstate /script.

1 Like

I did not, will it result in a permaban? or a temp one? gameplay ban or forums? not on here often and generally not for long either…

I was having fun though… giggling like a school girl over here.

But a troll that hate all macros and addons the say that the focus id wasnt in vanilla. Then we point out that everything it does could be doen in vanilla and we go round and round

1 Like

Well it wasn’t. it was a script allowing you to make any person a “focus” id by using the word focus…

Its fine. Im using him to bump the topic without it technically being spam.

“Pocket Healer” also has (at least historically) meant that a DPS or Tank-type had “a personal healer” following them around as they duoed content. Couples playing WoW often have one spouse playing as “a pocket healer” for example.

Heck for that matter, for the early stages of the beta while Asmond and Esfand were leveling together in the race to 30. Esfand being the paladin to Asmond’s warrior was essentially wound up acting as Asmond’s pocket healer on a number of occasions. (They aren’t restricted to healing only, it’s inefficient to do that among other things)

How does a focus frame make decisions for you? It’s a unit frame.

All it does is provide information, and a locus for macros to target. Macros you still have to trigger on your own.

Am I understanding you correctly, that the request is to add something that was implemented in TBC to Classic?

3 Likes

No changes

But you can’t have a focus frame for a target you need to keep CC’d because that unit frame might somehow make a decision for you. :rofl:

Nevermind being able to focus your CC target assignment and go about doing DPS, or healing, until it’s time to refresh the CC again is too much for some of these people. Never mind this capability existed in Vanilla and was widely used even then.

It just wasn’t part of the Stock UI, so it’s “a change” although they have to conveniently ignore that the Classic Client appears to actively prevent creation of such frames now, which also is a change. So “no changes” has a no-win scenario on this one, which ever side they take, they’re advocating a change.

/focus as part of the game API was TBC, however, it became part of the game API because it was in wide use and they were removing the means by which it had previously been created by.

Beta currently seems to exist in a realm where the TBC+ change where the ability to create unit frames is still removed, but they also removed the focus frame. Net result is we’re dealing with two different conflicting changes.

Blizzard isn’t re-implementing the scripting system needed for players to re-create the focus frames as they did in Vanilla(that’s a #change). Which means the compromise option is to go ahead and add it to the API so the net result on this issue can be #nochanges even if it is technically something that wasn’t a “stock” feature for Vanilla.

the actual focus unit frame didn’t come into the game until TBC.

People called it “focus” in vanilla but it wasn’t necessarily the focus target.

That allowed too much exploiting. What they did in 2.0 was define it themselves rather than letting players define it.

2 Likes

The devs aren’t perfect, oversights happen.

/focus being pulled likely was the end result of someone noticing it didn’t exist until TBC.

And nobody else realizing it was added because they were removing the functionality needed to create it. Functionality they did NOT restore to Classic.

I’d rather they add /focus into the game, and accept that #change over their restoration of the “authentic”(#nochanges) scripting capabilities that would otherwise need to be enabled in the client.

Objecting to focus frames on the grounds on multiboxers making use of AND #nochanges it is just bizzare against that backdrop. Because the no #nochanges people are literally advocating for several changes at that point. Multiboxers also were authentic to Classic. I’d rather they not exist, but I’d also rather not have the macro/scripting system not be as powerful as it was in Vanilla. So once again, just roll with the focus frame, there are legitimate in game uses for it.

I want focus frames for my own use, and I know numerous others in the same came, and I don’t multi-box(and neither do most of the others I know).

Understood, but the “ask” in this case is for the Blizzard implementation. The Blizzard version doesn’t make decisions for you.

Blizzard’s stance with the 2.0 changes was “one click, one action”.

1 Like

But…in pulling that in will they have to pull even more 2.0 changes in to support it ?

Only Blizzard can answer that.

We don’t know if they forgot to add it or didn’t add it on purpose.

2 Likes