Droidz

https://wrobot.eu/forums/topic/16294-path-server/#comment-71172

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/

Hello, Ebonhold doesn't run an original 3.3.5a client. Their Wow.exe is patched to load their own DLL inside the game (they use it for integrity checks and custom Lua functions). WRobot is made for the standard 3.3.5a client. Since everything worked before their server update, they most likely changed something in their client mod that blocks the bot. It has nothing to do with trial vs license, the timing is a coincidence. You can check that WRobot itself is fine by testing on another 3.3.5a server with a clean client. But on Ebonhold I can't do much against a modified client, sorry.

Hello, I just sent you a message with the card code.

Yeah, that's fair. Right now the regen sits once and tops up both health and mana together, there's no way to split them from the settings. I'm adding an option for it in the next update (regen health and mana separately), so a heal-only sit won't drink and a drink-only sit won't eat, while each still goes up to its own max. Once it's out you can turn it on from a plugin or your fight class with: wManagerSetting.CurrentSetting.SeparateHealthAndManaRegen = true; In the meantime you can already get that behavior, take the heal out of the food/drink settings and put it in your fight class.

Hi, Actions on path points do work, and your format is right (the c#: prefix). The likely issue is that the bot never really lands on that exact point, so the action doesn't fire. It validates a point from a few yards away and moves to the next one, and your points are very close together, so it passes that one without triggering its action. Try spacing that point out from the others first. If that doesn't fix it, share your profile and a log file so I can check.

Hi, It's not the default behavior, the bot only flies to your corpse when it can't make a ground path to it. You can try this plugin (not tested), put it in your Plugins folder and stay on a flying mount when you die: Fly to corpse when dead.cs using System; using System.ComponentModel; using System.Threading; using robotManager.Helpful; using wManager.Events; using wManager.Wow.Helpers; // Force the bot to fly back to its corpse (corpse run on a flying mount). public class Main : wManager.Plugin.IPlugin { private const float MinDistanceToFly = 30f; private const int AscendRetestMs = 5 * 60 * 1000; private const int MinActionIntervalMs = 500; private static bool _testedThisDeath; private static bool _isFlyingMount; private static int _lastAscendTick; private static int _lastActionTick; [ThreadStatic] private static bool _reentry; public void Initialize() { OthersEvents.OnPathFinderFindPath += OnPathFinderFindPath; Logging.Write("[FlyToCorpse] Loaded."); } public void Dispose() { OthersEvents.OnPathFinderFindPath -= OnPathFinderFindPath; Logging.Write("[FlyToCorpse] Unloaded."); } public void Settings() { } private static void OnPathFinderFindPath(Vector3 from, Vector3 to, string continentNameMpq, CancelEventArgs cancelable) { if (_reentry) return; _reentry = true; try { var me = wManager.Wow.ObjectManager.ObjectManager.Me; if (me == null || !me.IsValid) return; if (!me.IsDeadMe) { _testedThisDeath = false; _isFlyingMount = false; return; } if (!me.IsMounted) return; Vector3 corpse = me.PositionCorpse; if (corpse == null || corpse.DistanceTo(Vector3.Zero) <= 0) return; if (to == null || to.DistanceTo(corpse) > 12) return; if (corpse.DistanceTo(me.Position) < MinDistanceToFly) return; int now = Environment.TickCount; if (_lastActionTick != 0 && (uint)(now - _lastActionTick) < MinActionIntervalMs) return; if (!me.IsFlying) { bool mayTest = !_testedThisDeath || (uint)(now - _lastAscendTick) >= AscendRetestMs; if (!mayTest) return; _testedThisDeath = true; _lastAscendTick = now; Move.JumpOrAscend(Move.MoveAction.DownKey); Thread.Sleep(Others.Random(300, 700)); Move.JumpOrAscend(Move.MoveAction.UpKey); Thread.Sleep(Others.Random(300, 700)); _isFlyingMount = me.IsFlying; } if (!me.IsFlying) return; to.Type = "Flying"; _lastActionTick = now; cancelable.Cancel = true; } catch (Exception e) { Logging.WriteError("[FlyToCorpse] " + e); } finally { _reentry = false; } } }

https://wrobot.eu/bugtracker/wow-lk-gatherer-storm-peaks-r1625/

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/

Hi, Share the full log file from that druid (the .html in the Logs folder, from a session where it got stuck). Also tell me if it gets stuck at the same spot. You can also turn on Radar3D in the Map tab, it draws the bot's path and what it's targeting directly in-game, so you can see where it's trying to go when it gets stuck.

Hi, That error means the bot can't reach our server. It is almost always a VPN or proxy, your antivirus, or your firewall blocking the connection. Disable your VPN, add WRobot to your antivirus and firewall exceptions, and make sure you are on the latest version, then try again.

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/

Hi, The crash comes from Epoch's custom client and its anti-cheat conflicting with WRobot's.

Hi, Which quester profile are you using? A special objective like absorbing those elementals usually needs a specific step in the profile, the bot doesn't know that custom interaction on its own, so if the profile just kills or interacts normally the absorb won't count.