That is a function. The OP and their partner are talking about /script usage.
Ah yes Fakespeare
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.
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
Well it wasnât. it was a script allowing you to make any person a âfocusâ id by using the word focusâŚ
Blazilz you realize you can be reported for harassment? I suggest you stop.
Its fine. Im using him to bump the topic without it technically being spam.
I didnât expect you to double down on the dishonesty. The term âpocket healerâ in no way implies that dual-boxing or macros are being used.
Who is the one being dishonest puppy kicker? Stop kicking puppies.
â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)
Way too good, unintentionally good. The game shouldnât be making decisions for you
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?
No changes
I have no interest in multiboxing and want the focus unit frame which replaced the old scripts to be in classic though if they unlocked the scripts instead I would get an addon.
I want it for dispell, interupt, and cc macros, and healing in pvp.Maybe if you werent so busy kicking puppies you would see that.
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.
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.
Did this come in Patch 2.0.1?
/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.
Itâs funny how a couple of people know more about wow then the devs themselves. If it was in they would left it in so there was a reason they took it out. Anyone saying they are wrong without any information to back it up is incorrect.
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).
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.
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â.
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.