Matenia

Use a Lua script for the condition with UnitDebuff. The TBC ret paladin fightclass here on the forums does the same.

Hey, I use slightly different code (Hook.IsLockAllowed) now and UnlockFrame(true). It seems to work on Win10, I will get back to you, if it bugs again and send you my VS project

Those are combatlog events, which currently aren't supported. I already filed a bug report with Droidz.

This works when making the Settings constructor public, for some reason.

For the time being (I just use C# and it works fine, btw), you can use Lua RunMacroText("/cast !Shoot")

Same for Automaton. It worked on MoP, but doesn't work on TBC.

Tested for TBC.

Botting anything but AV and EotS is suicide. I wouldn't recommend botting any BG with small maps where people rely on individual players a lot.

Like the log says... you'll need a fightclass. Did you actually think you can just afk BGs and do nothing? Enjoy getting banned.

Like it was being said in all the other 10-15 threads with this problem, turn off the "only queue if party leader" option.

https://github.com/haimanman/SciTE-ru-jx3/blob/master/api/LuaWoW.api this is for patch 3.0, but vanilla has most these functions You cannot choose to run to a target with Lua alone (unless you build a framework around movement functions). You'll need to use the C# functions the bot provides. You can join Discord and ask questions there.

@Droidz this is a problem with TBC 2.4.3, where on players HaveBuff doesn't work (I tried C# API too). It works on NPCs. Or at least, in Battlegrounder mode this is bugged, but doing it normally while leveling works fine.

If you keep your Search Distance low and turn off pathfinding altogether in your general settings, it will ONLY follow the path you create, given you do create a path and not several hotspots. The bot mainly functions through hotspots, at which it tries to find enemies in WoW's objectmanager (basically any unit your client knows). If it finds a unit, walks to it, then finds another, it will keep chasing them far away from your path.

Disable only queue if party leader or whatever the option is.

If you have a fightclass, you can add a condition of type Lua script.

@Droidz Is there any way I can prevent the bot (in my fightclass) to chase enemies in BGs? I'm a healer and want to do some healing. Target selection and all works in my fightclass, but the bot keeps targeting opposing faction players, chasing them and then not targeting/healing any of my teammates. It barely does what it should, unfortunately. How can I fix this?

The 2.4.3 version of wManager.dll doesn't seem to have a class EventsLuaWithArgs. Any current workaround for that? I'd love to read combatlog events to automate stuff for a PvP fightclass.

The TBC version of wManager.dll seems to be missing this feature (Lua events with args) entirely. @Droidz

Disclaimer: OP messaged me in private, and I didn't test this: local spellTable = {8122,5782,5246,5211,22570,19577,119381,853,408,1833,89766,107570,15487,2139}; hasDebuff = false; for i=1,40 do local name, rank, icon, count, dispelType, duration, expires, caster, isStealable, nameplateShowPersonal, spellID = UnitDebuff("party1", i); for k,v in pairs(spellTable) do if spellID == v then hasDebuff = true end end end return var is hasDebuff, search value is true (could also make this 0 and 1). Then the code is RunMacroText("/cast [@party1] spellName") Both the check above and this spell need to be Lua code.

You can just execute the Lua code RunMacroText("/use 13"), that way no macro setups are required and your users don't need to create macros.

You could multiline by using \n for linebreaks. Or you could create a small addon with a public function that executes all these things, then use the Bot's Lua API to call that function.