Pudge

I've noticed that npc vendor priority is higher than npc repair. Bot just chooses a vendor first and it doesnt care if the repair is closer by distance than a vendor. Why so?

Often gets stuck when trying to sell to a mammoth, if the bot is too high above the ground and the totown state is called, while the bot goes down, it adds a vendor on a mammoth to the blacklist and then gets into a cycle of endless attempts to sell trash to NPC on a mammoth, which is blacklisted at 120 minutes. Please fix it, cause of this bug, bots that do not have a mammoth farm more gold than those who have it.

After using SpellManager.UpdateSpellBook the bot doesn't see new learned mount spells. SpellManager.ExistSpellBook returns true for new mount spells only when the bot is restarted (after closing). @Droidz Can you fix this, or are there other ways to see freshly learned mounts without restarting bot and without using lua, only c#?

Since the latest updates, checkboxes (✓) have become invisible until the field in the relogger is running. Please fix that. This is only on windows classic theme. For clarity, I am attaching a video.

Hi. The function Vendor.BuyItem(); does not work correctly.Instead of the required amount,just one good is always bought.

This appears after stopping bot using stop button and launch bot again, after this messages bot doesnt do anything until kill the process and start the bot again. It happens very often. I made the function in my plugin that kill wrobot.exe after this messages appears in log, but the plugin is usually loaded after these entries appears in log and in 99% of cases this does not work. [D] 12:12:33 - [FSM] State wManager.Wow.Bot.States.Idle already launched, ignore it.[D] 12:12:33 - [FSM] State   already launched, ignore it.[D] 12:12:33 - [FSM] State wManager.Wow.Bot.States.Trainers already launched, ignore it.[D] 12:12:33 - [FSM] State wManager.Wow.Bot.States.Talents already launched, ignore it.[D] 12:12:33 - [FSM] State wManager.Wow.Bot.States.FlightMasterDiscoverState already launched, ignore it.[D] 12:12:33 - [FSM] State wManager.Wow.Bot.States.ToTown already launched, ignore it.[D] 12:12:33 - [FSM] State wManager.Wow.Bot.States.FlightMasterTakeTaxiState already launched, ignore it.[D] 12:12:33 - [FSM] State wManager.Wow.Bot.States.ProspectingState already launched, ignore it.[D] 12:12:33 - [FSM] State wManager.Wow.Bot.States.MillingState already launched, ignore it.[D] 12:12:33 - [FSM] State wManager.Wow.Bot.States.Farming already launched, ignore it.[D] 12:12:33 - [FSM] State wManager.Wow.Bot.States.Looting already launched, ignore it.[D] 12:12:33 - [FSM] State wManager.Wow.Bot.States.Regeneration already launched, ignore it.[D] 12:12:33 - [FSM] State wManager.Wow.Bot.States.FarmingRange already launched, ignore it.[D] 12:12:33 - [FSM] State wManager.Wow.Bot.States.LootingRange already launched, ignore it.[D] 12:12:33 - [FSM] State wManager.Wow.Bot.States.BattlePetState already launched, ignore it.[D] 12:12:33 - [FSM] State wManager.Wow.Bot.States.IsAttacked already launched, ignore it.[D] 12:12:33 - [FSM] State wManager.Wow.Bot.States.MyMacro already launched, ignore it.[D] 12:12:33 - [FSM] State wManager.Wow.Bot.States.Resurrect already launched, ignore it.[D] 12:12:33 - [FSM] State wManager.Wow.Bot.States.Pause already launched, ignore it.[D] 12:12:33 - [FSM] State wManager.Wow.Bot.States.Relogger already launched, ignore it.

I don't know if this can be called a bug, but before, when the bot died near the spirit healer, and the corpse was in the 40 yards (resurrection zone), the bot didn't use the healer and resurrected at the corpse. Now, even when the corpse lies within reach, the bot uses the healer, ignoring the availability of the corpse. It would be nice to do as it was before. After the latest updates: