Is there a way to /targetnearestenemy and /targetnearestenemyplayer in one macro?
Currently have to make two targeting macros to depending on pve or pvp. Would prefer one thats smart to determine if enemy is npc or player.
Is there a way to /targetnearestenemy and /targetnearestenemyplayer in one macro?
Currently have to make two targeting macros to depending on pve or pvp. Would prefer one thats smart to determine if enemy is npc or player.
I just do tab and shift tab for one or the other. Tab for players 'cause I PvP more often.
If you want to do both, target nearestenemy should do both.
You want the macro to only target players and target npcs afterwards?
I don’t think you can, since both player and NPC would be in range of you. Do what Drougen suggested. You don’t even need a macro either, just keybind the targeting.
Basically, world pvp. If there is one mob and a enemy player jumps you, i want targeting to select the player.
/targetnearestenemy is only for pve
No target nearest enemy also targets players. That’s all I use, I don’t even have target nearest enemy player keybound. If you want to differentiate then keybind target nearest enemy player to something.
I’m wondering if naming my pet same name as myself messes up with targeting macros like it did in vanilla
So you are saying /targetnearestenemy works on players, yet the newer scan target does not…?
WoW
Go to your keybindings, stop using macros. Key bind your targeting. Target nearest enemy works are any neutral and hostile NPC or player. You can also separate keybind target nearest player, once again without using a macro.
Macros are superior to single keybindings. Thats why they are there. I think I have a macro that works now.
Ok if it works for you, but I completely disagree for targeting. Glad you found something.
I’d love to see it. The basis of the macro system is that there is never a “if this, then that” functionality. They can’t make any decisions, the only way to do it (what you originally suggested) in a macro is to add a key modifier so it does one or the other. In these cases, I just bind the modified key to what I want it to do. It’s more simple than writing a macro, works exactly the same, and is often easier to make changes later.