You might be able to but that would be more work and no logical sense for them. Focus however already exists in the Retail API. If they wanted to make it more authentic to Vanilla, they’d allow us to define our own unit IDs. But alas, the security model prevents that because we’re not getting the genuine API.
The fact remains however, that the target unit ID didn’t exist in Vanilla, yet we’re getting that in Classic. The only way to avoid getting it is to disable all macros in Classic. Which is an even less authentic change.
While also limiting the exploitability of the script features. The title of the post is misleading and disingenuous. Focus ID wasn’t in vanilla and was deliberately not put in classic.
We’re not asking for the old macro system. We’re getting the retail API.
The request is for a single user-selectable unit ID. You can call it whatever you like, but we had it in Vanilla, it was re-added to support the functionality in TBC, and Classic is the only version of WoW that doesn’t have the functionality.
We had a Focus Addon for TBC on private servers… The API to make a focus addon should work at least in TBC. The only thing that doesn’t work in TBC even with addons is arena target 1 2 3. Blizzard fix this before you release TBC at least.
Considering that Focus ID is in current API and all the other ID’s are in classic but that one isn’t speaks for itself. Nothing about my statement is disingenuous. You just don’t want it to be true.
You can infact get the focus frame addon for vanilla private servers and could get it in vanilla. The id is named after the addon not the other way around.