Using focus target for multiboxing is harder than just using a program made for it.
lol yeah, youâre not wrong thatâs for sure
This seems like a harder change for them to address, isnât it? Right now the Classic code is mirroring pretty current code, how hard would this be to implement?
Would this break the game if they tried to put this back in? I always heard programmers say they fix one thing and break two more things.
I donât see what the big deal is. There were lots of /script commands that were around in vanilla that wonât be around this time. Would I like to have all my old macros back? Yes. Am I going to get them? No.
they wont. like i said before, this is the same thing that broke addons like NPCscan, due to the auto targeting. it is part of their anti cheating software, like what prevents wall jumping. basically this
the current code is going to stay in place, for things like this.
I am not even asking for the full functionality back. Thought it would be easy for them to do. I just want them to reenable the focus unit id thats still in retail wow.
They purposely disabled it. Cause its in the modern API. So what does that tell you?
Some examples:
Re-banish same target even if youâre dpsing something else. Casts Banish on the focus without changing the actual target.
/focus [nomodifier:alt,target=focus,nodead,harm] focus; target
/cast [target=focus] Banish(Rank 2)
Re-seduce with succubus:
/stopmacro [nopet:Succubus]
/petfollow [modifier:alt]
/cast [modifier:alt] Curse of Shadow; [target=focus,nodead]; Curse of Shadow
/focus [nomodifier:alt,target=focus,nodead,harm] focus; target
/cast [target=focus] Seduction
But wasnât in vanilla, so shouldnât be in classic
Neither was the target
ID.
In fact there were no macro conditionals in Vanilla at allâŚ
They were all added in TBC, and weâre getting that API.
uhh
And not the focus⌠I think that really says something, you just donât want to hear it.
But you dont want what was in classic either. Pick a side. Do you want what was in classic the ability to create ids or the thing they replaced it with /focus.
totally against it
And Blizzard used the name to define the unit they provided, so that the functionality could could still be used.
Neither. They already stated they would limit the classic API and this is how they are. I agree with their choice. I can admit it would be useful and I would use it if it was in.
Donât say it was in though cause Focus ID wasnt in.
Blizzard also decided not to include it in Classic API yet here we are.
Iâm chalking this all up to one of those things they changed just like with the current interface options and the improved graphics.
Can you use other /script functions? If yes, could this be something they intentionally left out? If so, they must have a reason.
But you dont want what was in classic either.
same thing i seen from people who were against wall jumping. no lie. i guess if you arent okay with exploitative game play that was the fault of old rigs, faulty software and limitations at the time of its production> you dont want vanilla at all.
its like saying if you arent okay with OTHER people getting an advantage over you, while you try to be as honest as possible, you clearly arent part of the team/group/community
such dismissal amazes me.
Iâm chalking this all up to one of those things they changed just like with the current interface options and the improved graphics.
Can you use other /script functions? If yes, could this be something they intentionally left out? If so, they must have a reason.
Yes they intentionaly blocked it in burning crusade but they replaced it with several premade ids. One of those was focus. Since we cant make our own IDs which im fine with I want them to include the focus ID they created so that things they wanted to be available still worked.