All you need to do is send a JSON POST with a “Name” value set to the players name (and server), e.g. Shibah-Spirestone to the no changers public API:
api.classiccommunitynochangers(dot)org/v2/
Easy one to point at is Fesz.
He doesn’t want the Vanilla Scripting system, so he’s #nochanges, except when it comes to scripting automating the game.
But as we’re seeing with /focus being added into the API, because the scripting system was changed, he’ s opposing it becuase it was added in 2.0.x and thus adding it is a #change so he’ll fight it.
“A man gotta have a code”
-Omar
An implementation that was added in TBC.
1 Like
Except that blizzard also had an implementation in vanilla.
2 Likes
Every single part of the UI was added in TBC. You can’t get past this. I get it. You’ve decided that anything I suggest anywhere, is wrong, because I don’t want AV 1.5. But you really need to stop making yourself look like a fool here.
I thought Fesz was hurt in the butt over AV 1.12 so he turned into an advocate of literally no changes from 1.12?
It seems there are two camps:
-
No changes from Vanilla. If something changed during Vanilla and can’t be mirrored with the phased content release system, it should defer to its 1.12 state.
-
Make it exactly like 1.12. Full stop. All raids released, no AQ gates, 100% 1.12 or unsub.
People in group 2 are probably just passive aggressive crybabies.
3 Likes
No, fesz literally argues against everything, even when you have 100% proof to the contrary.
Blizzard implemented UnitPower in what, 6-7x but it is being used in Classic over UnitMana which was in Vanilla. Same thing different name just like…
1 Like
Not the implementation that is being requested.
The modern infrastructure is incompatible with the older scripts and macros.
We KNEW that the change in infrastructure could prevent some scripts, macros and third party add-ons that worked in vanilla from working in Classic.
Focus appears to be just one of those things.
Not having focus does not prevent dual boxing, multi-boxing, healing “off targets”, chain Ching, etc. It might be a bit more inconvenient to do and require more effort and attention, but it CAN be done without focus.
If Fesz wanted it 100% like 1.12, then he’d be advocating for the unrestricted scripting system that existed at that time in lieu of the focus frame.
He isn’t doing that, he’s letting that one lie, and instead fighting against implementing the focus frame.
There is absolutely nothing in the modern infrastructure that would prevent focus targeting as it is included in the modern infrastructure.
The focus frame is still there, just commented out last I looked.
1 Like
Is target of target there and active ?
That would be the right focus that 2.0 implemented.
So what does that make him? A proponent of no changes from what Blizzard has put in (so far)? Essentially a Blizzard shill?
Cause in this case (and others he argues [poorly] against), he’s actually advocating for change in Classic from Vanilla.
I guess maybe he’s a pro changes advocate then actually?
Actually, yes it is.
We know. We’re not asking to use the old scripts.
We’re not asking to use old addons.
Please just stop making a fool of yourself.
Well, surprise, you’re demonstrating you don’t know what you’re talking about.
The “infrastructure” isn’t preventing Blizzard from allowing these things to work. It is that Blizzard deliberately chose to disallow most of these things from working. Because they couldn’t control what players were doing with them, up to and including near complete automation of gameplay.
It just happened that in order to get some instances of that going on, there often was “collateral damage” along the way, which resulted their needing to create new means of accomplishing certain things they didn’t have problems with.
I’m not understanding what you are meaning by “right focus”.
TargetFrame.xml now
TargetFrame_CreateTargetofTarget(self, "targettarget");
TargetFrame.xml, 1.12
<Button name="TargetofTargetFrame" toplevel="true" parent="TargetFrame" movable="true" enableMouse="true">
The focus unit ID has been removed (or disabled, can’t tell because server) which means all of the focus elements can’t work, because Secure Frames require an anchor unit ID to function off.
Addons can’t recreate the frame without the unit ID, so the request is only, and has always been only:
Please reinstate the focus unit ID, with slash command and key binding.
(We could probably make the slash command and keybinding ourselves but the general player shouldn’t have to.)
target of target is the focus.
In the old vanilla code you could make “focus” anyone you wanted…it was player defined.
1 Like