It sounds to me like you are admitting that I am correct.
“Built in” focus frames were added in TBC and were not part of vanilla.
During vanilla focus functionality required scripted macros or third party add-ons which the old infrastructure supported. The modern infrastructure does not support those macros or third party add-ons.
Are you suggesting that Blizzard either change the modern infrastructure or add a TBC feature to Classic in the name of convenience?
That’s because you can’t accept that your own statements are wrong. You can frame your white lines however you like but the fact of the matter is that you are advocating for a “non-Vanilla” change for your own preference.
If anything, this is a repudiation of all your positions as Convenience Police, because you are literally declaring that Classic should not recreate Vanilla.
No, I’m saying they return the thing they already deleted from the API. Even if they don’t put the frame back in, the unit ID focus existed in Vanilla through scripting, and their choice to change Vanilla by using a modern API requires adjustments to make it ‘autnentic’. One of those things that needs to be included is the focus unit ID because they are not giving us the old scripting model.
I am advocating for a more Vanilla experience, and you are suddenly in the #YayChanges crowd.
In summation, “Multiboxing while not prohibited is also not supported [in ToU]”
Here is a response by a blue post on multiboxing (same post, different responses):
Also an interesting tidbit from the blue post:
"…One could argue that the frustration that a single multiboxer can cause actually costs subs, since a player who is frustrated that their character was killed by a single person (5 characters, but single real world person), may leave because of it. " - Vrakthris
From your first post:
Multiboxing is not unique to World of Warcraft, it has been happening in these types of games for a very long time. The fact of the matter is that there is nothing in our policies that would prohibit such actions. You are allowed to have multiple World of Warcraft licenses as well as Battle Net accounts. If that was prohibited that would also restrict minors from being able to play the game along with their parents as the account needs to be registered to the parent or legal guardian of a minor that is under 13. So if they allowed their child to play they would be restricted from doing so, if such policies did not otherwise allow for it.
From your second post:
As noted, we have a clause stating that we may close an account for any reason we choose. We do not need to be vague just in case we change our minds. Our stance on multiboxing has existed since the very beginning and I can say with a great deal of certainty that if we ever decided to prohibit that particular play style that we would announce it and provide a grace period before the policy went into effect.
Thank you for proving my point in exquisite detail.
Glad I could help ![:smile:](https://d38bqls1q93fod.cloudfront.net/en/wow/images/emoji/twitter/smile.png?v=6" ":smile:")
But mainly just wanted to point out that while they applaud multiboxers, they do not support them and this can be extended to any providing functionality that would make multiboxing easier or out of scope of the project which is to put the original game on the new engine (API and all) which they have already described in detail with Ion and other developers.
Focus has a number of other uses, which I detailed in previous posts which garnered a general “meh”.
This post has been quite successful in getting the message on the radar though, and each time someone jumps in to repeat the same tired argument or dump on multiboxing, the chance that my healer can use focus in Raids, and my mage can use focus when CCing, increases.
Those mental gymnastics and sidestepping which you are doing to justify asking Blizzard to either change the modern infrastructure or add a non vanilla feature to Classic in the name of convenience are almost impressive.
“I’m not asking them to change the modern infrastructure. I just want them to add X (which does not exist in the modern infrastructure) to the API.”
Honesty is not your strong suit, I see.
We already KNEW that the modern infrastructure could affect some old macros or third party add-ons. We already KNEW that some things which may have been possible during vanilla would not be possible in Classic due to the modern infrastructure.
It seems that unless Blizzard is willing to change the modern infrastructure or open Pandora’s box by adding TBC elements to Classic, focus may very well be one of those things.
Um, focus does exist in the modern infrastructure. That’s the point.
The mental gymnastics to interpret anything I said in that way is impressive.
Indeed, and I hope that this draws notice, really. If it does, then you’ll get an official response that says “No” or “Yes”. If “Yes”, great! If “No”, I can’t imagine that you’d take “No” for an answer. ![:frowning:](https://d38bqls1q93fod.cloudfront.net/en/wow/images/emoji/twitter/frowning.png?v=6" ":frowning:")
But, it’s an easy give that you’re being pretty defensive from this response alone, but as long as we can have an objective and well-purposed discussion, I’m all for keeping it going! ![:slight_smile:](https://d38bqls1q93fod.cloudfront.net/en/wow/images/emoji/twitter/slight_smile.png?v=6" ":slight_smile:")
Actually, that’d be fine. I’d do what I said and discontinue the second account because its useless to me at that point, since I don’t want to use cheating software to dual-box.
As I’ve said a number of times above, this isn’t a “I demand you do it” post. Its a “Just making you aware of the real consequences” one.
If I can’t use my 2nd account in any viable way, I have no reason to pay for it. It worked in Vanilla and every expansion since, but why would I if it doesn’t work in Classic.
If those old macros or add-ons are not compatible with the modern infrastructure, then would it not be changing that modern infrastructure to add that compatibility?
No because they added the functionality to the modern infrastructure in 2.0.1. The same patch that they removed the ability to do it with scripts.
There has never been a time in WoW’s history when this could not be done by one or the other means, until the Classic client. They literally removed the element from the modern infrastructure for the Classic client.
So what you’re saying isn’t just nonsensical, its provably wrong.
Would adding the ability to use scripts to the modern infrastructure not be changing that infrastructure?
Clearly you’ve lost track here. I’m asking for the removal of the focus unit ID from the modern infrastructure for Classic to be reverted. To give us a genuine Vanilla-esque capability.
No Dual-boxing! Nice!
So, ate you saying that you’re asking that the modern infrastructure be changed by adding the focus unit ID to it?
The modern infrastructure already has the focus unit ID in it, except for the implementation they’ve put into Classic.
Vanilla had it. Retail has it. Classic does not.
If it helps, the reasoning for the removal of FocusUnit() is explained here (I’m not sure of any Blue Posts that reference it but history shows the explanation was added in 2007), but it appears to have been a prime use by botters and is why it was removed:
LINKHERE_https://wowwiki.fandom.com/wiki/API_FocusUnit
I do not expect them to re-implement this functionality if it was primarily used as a means for botters and would only reopen the can of worms.
Um. Its still there in Retail. It has not been removed because of botters at all.
FocusUnit still exists, it’s just in protected code. Which I would expect if they reverted the change from Retail.
I am only referencing what is in the API wiki from 2007, so unless we have a way-back machine, I can’t really say more.
" However /RunMacroText("/focus") can be used still."