Droidz

If the problem always occurs in the same zone, blacklisted this zone (some zones can be badly supported by the bot). It is possible that your profile is badly or not adapted to your server/game version, in this case try with another. If you have this problem with all profiles it is probably installation or configuration problem. I close this request (these useless to continue this discussion), if you cannot solve your problem open a new request with your logs files, a better description of your problem with screenshots / video .

Hello, blacklist zone if zone is bugged

hi, maybe try to replace "ObjectManager.Me.InCombat" by "ObjectManager.Me.InCombatFlagOnly"

check also if your profile don't change this value

Hello, in advanced general settings tab "looting..." put bigger value at the options "max units near..."

If problem is not resolved share updater log or screenshot of the error

Hello, try to restart your computer and try to update again after

Thank you, you need to wait next update for the fix

I found why, wait next update

You have try to remove wow cache folder? how long have you had this problem?

Hi, If I'm not mistaken, by default Wow uses 0 (and since a few updates the bot forces the use of 0 internally)

Hello, Disable all Wow addons, all WRobot plugins and share your log file please ( https://wrobot.eu/forums/topic/1779-how-to-post-your-log-file-with-your-topic/ ).

Hello, Disable all Wow addons, all WRobot plugins and share your log file please ( https://wrobot.eu/forums/topic/1779-how-to-post-your-log-file-with-your-topic/ ).

Hello, you have try without fightclass? You get this problem all time when bot start fight?

Hello, try again

Hi, yes next time that you get this problem check if NPC is not blacklisted (use radar3d with option to see blacklist enabled). It is recent problem for all? only in Wotlk? you have try to put bigger interact distance?

hello, send me screenshots of untranslatables fields.

Hi, When you edit "wManager.wManagerSetting.CurrentSetting" change is instant. Maybe quest profile change settings, if you save settings when running, quester cannot restore default settings

If you can try with new update and tell me if problem is resolved

I am sorry I don't understand why you have this problem (and I don't remember anyone reporting a similar problem to me)

Hi, i try to fix it tomorrow

You haven't changer wow or wrobot of folder? maybe one folder name use special char or access rules

I updated Windows and I use more recent version, I don't get problem. I really think it's a configuration issue. Check that the path to Wow and WRobot is correct in the settings of the relogger

Hello, the problem is that you use grinder and you cannot use option to mount after all farm. try to use this plugin for force to use this option: using System.ComponentModel; using robotManager.FiniteStateMachine; using wManager.Wow.Bot.States; public class Main : wManager.Plugin.IPlugin { public void Initialize() { robotManager.Events.FiniteStateMachineEvents.OnRunState += delegate(Engine engine, State state, CancelEventArgs cancelable) { try { if (state is Farming) ((Farming)state).AutoMountIfSuccess = true; } catch { } }; } public void Dispose() { } public void Settings() { } } Main.cs

try to put 45 (instead 40)