Droidz

The last possibility is that it's caused by a wrobot plugin or the fight class. Otherwise, I'm sorry, I don't know what could cause this type of problem.

Try to use the shortcut "WRobot (DX hook)" to launch the bot.

Hello, Your client path shows "TBC-2.4.3.8606-enGB-Repack" - repacks are often slightly modified clients (even if they look "clean"), and that's very likely what's causing the crash. Try to find an original unmodified 2.4.3 client (not a repack) and test with that. That should fix it. No, Vulkan won't help here, the issue is at the memory/hook level, not graphics related.

Hello, Could you please share the full log file of the session where you encountered the issue? You can find instructions on how to post your log file here: https://wrobot.eu/forums/topic/1779-how-to-post-your-log-file-with-your-topic/

Changed Status to Fixed Changed Version to All

Hello, The hosting provider is experiencing a technical issue with their infrastructure. The service will return as soon as the machine hosting the pathfinder server is back online.

Hello, Could you share the versions/builds (of the game) that your servers are using?

Hello, What do you mean by "trying to log out" exactly? Is WoW going AFK and showing the disconnect dialog because the bot isn't sending any input? If that's the case, try enabling "Use Lua to move" in the general settings. Can you also share a log file (from the Logs folder) so I can see what's going on?

Hello, Can you share a log file (from the Logs folder) showing the issue? It would help see what's happening when the bot says your mining level is too low. Also, which exact WoW client version is this (check the game login screen, bottom left)? And which server? For the ground mount running in circles - are you using "Use Lua to move" in the general settings? On some private servers CTM (click to move) behaves differently and can cause circular movement.

Hello, The GetReactionTowards NullReferenceException typically happens on private servers that use custom NPCs with faction template IDs not present in the bot's internal database. The bot can't determine if the mob is hostile or friendly, so it just skips it.

Hello, You can do this with a C# plugin. Save this as a .cs file in your Plugins folder (no tested): using System; using System.Collections.Generic; using robotManager.Helpful; using wManager.Wow.Helpers; using wManager.Wow.ObjectManager; using Math = System.Math; public class Main : wManager.Plugin.IPlugin { private bool _isRunning; public void Initialize() { _isRunning = true; EventsLuaWithArgs.OnEventsLuaStringWithArgs += OnCombatLogEvent; Logging.Write("[MoveOnSpell] Started."); } public void Dispose() { _isRunning = false; EventsLuaWithArgs.OnEventsLuaStringWithArgs -= OnCombatLogEvent; Logging.Write("[MoveOnSpell] Stopped."); } public void Settings() { } private void OnCombatLogEvent(string eventid, List<string> args) { if (eventid != "COMBAT_LOG_EVENT_UNFILTERED" || args.Count < 9) return; string subEvent = args[1]; string spellId = args[8]; if (subEvent == "SPELL_SUMMON" && spellId == "95074") { Logging.Write("[MoveOnSpell] Detected spell 95074, moving away!"); var me = ObjectManager.Me.Position; float angle = (float)(new Random().NextDouble() * Math.PI * 2); float dist = 10f; var safePos = new Vector3( me.X + (float)Math.Cos(angle) * dist, me.Y + (float)Math.Sin(angle) * dist, me.Z ); MovementManager.Go(new List<Vector3> { safePos }); } } } This listens to combat log events and when it sees SPELL_SUMMON with spell ID 95074, it moves 10 yards in a random direction. You can adjust the distance if needed. If the random direction sometimes sends you into a wall or off a cliff, you could replace the random angle with a backward movement (opposite of your facing direction) instead.

Hello, the problem should be resolved.

Hello, Yes, it's a typo that made it into production a long time ago. Unfortunately, fixing it now would break all existing FightClass profiles (XML serialization relies on the exact property name), so it has to stay as is. Sorry for the lost time debugging, I understand the frustration. I'll add a note about it in the documentation.

Hello, This problem should be resolved.