Matenia

public static ulong StartFight(ulong guid, bool skipIfPlyerAttackedButNotByTheTarget = true, bool managerMovement = true, bool stopIfPlayerTargetChange = false, bool rotationBot = false) Maybe some of these parameters are responsible. I also saw that wManagerSetting.CurrentSetting.DetectEvadingMob is considered.

Wrobot has an option like "can attack units already in combat" that might play into it. There's also a plugin for attacking tabbed targets of a main character. You might be able to look at the source or decompile it. Also, StartFight has a bunch of arguments

This fixes it. Weird bug though.

Why not post a tutorial here?

Read your log file, you need to run every monitor at 60Hz and the game with vsync

It used to happen on an older version of wRobot. Droidz fixed it. The current bug only happens in the way I explained it. Tested it myself plenty of times.

Also, I know I don't license any of my stuff, but it'd be great if you could release what you're making so others can profit from it the same way you have from my code :)

Yes, but I am explaining why it runs to NPCs again. It's trying to get as many queues as you have set NPCs, but Warmane only allows 2 so it keeps running

Would it be detectable, if I created a reference to the original function on startup (say, on /reload) and then only called that function directly through Lua (which would be unprotected Lua call)? If not, that's something I could do. Basically like this: EventsLua.AttachEventLua(LuaEventsId.PLAYER_ENTERING_WORLD, context => Lua.LuaDoString(@" if not _CastSpellSafe then _CastSpellSafe = CastSpellByName; end ")); Lua.LuaDoString("if not _CastSpellSafe then ReloadUI() end;"); Lua.LuaDoString($"_CastSpellSafe('Polymorph', 'focus');");

At 70% to 70% it can't start drinking... Just set it to 55 to 95, make sure the names are set correctly and you don't use a plugin like iEquip that overwrites drink.

At 1% minimum, it would only start drinking if you drop below 1% mana after combat. So Just do 55% to 95%. It will start drinking if you drop below 55 and until you've reached 95% before it gets up and fights again. This is a common question, use the search next time.

https://marsbars.gitlab.io/unoffical-wrobot-api-docs/api/wManager.Wow.Helpers.AuctionHelpers.html

Instead of iterating through WowPlayers using the Party API, just use ObjectManager.GetObjectWoWPlayer() and find one with your character's name.

It's an old product that hasn't been available in a while (wRobot was abandoned for retail servers). The name is therefore a bit confusing, but the subscription was lifetime (not yours, but wRobot for retail).

Your subscription expired on August 31st 2018. Of course you can't use it. It literally says "Status: Expired".

This is incredibly helpful. They probably give you a mind-control buff to see if you will still try to attack enemies (which are now friendly or neutral). You can still avoid attacking friendly players and try to attack enemy mobs (and/or if they are suddenly neutral, you can say something in chat automatically or make your bot wake you up, post to discord etc). Edit: If they change up the buff by adding customs spells, just getting the buff name/id wouldn't be enough - hence my suggestions.

Your thread is probably waiting for the ObjectManager to update (which happens on a different thread and is synchronized, therefore a locked operation). Either create a deep copy of the current ObjectManager and use that instead of yours, cache which spells you already know or make your fightclass thread sleep until just after global cooldown ends so that "waiting periods" for ObjecManager updates during your rotation have less of an impact. If you don't understand what I'm saying, this is too advanced for you and I recommend either buying a fightclass or trying to only run a single bot with both WoW and the bot having high process priority so all actions are executed faster overall.